JIRA — Software Testing QuestionHub #12

Who is reported in Jira?

In Jira, a “reporter” is the person who originally creates a new issue or task. The reporter is typically the person who has identified a problem or task that needs to be addressed, and is responsible for entering the initial details of the issue into the Jira system. This can include information such as a summary of the problem, the type of issue (e.g. bug, task, feature request), and any relevant details or attachments. The reporter is also responsible for assigning the issue to the appropriate person or team for further action.

Once an issue has been reported, it can be viewed and managed by other members of the team, such as developers, project managers, or QA engineers, depending on the specifics of the project. The person or team who is responsible for working on the issue will be able to see the reporter’s name, and can contact them if they need more information or clarification.

Jira also enable reporter to update the issue, once the work is done, based on the project settings, can close the issue or make it as resolved.

Get Software Testing Tips

How to create sprint in Jira?

In Jira, a “sprint” is a period of time during which a specific set of tasks or issues will be completed. Here’s an example of how you can create a sprint in Jira:

1. Go to the “Sprints” page in your Jira project. This can typically be found by selecting “Scrum” or “Kanban” from the main navigation, and then selecting “Sprints.”
2. Click on the “Create sprint” button, or select “Create sprint” from the gear icon in the top-right corner of the page.
3. In the “Create Sprint” dialog box, enter a name for the sprint and select the start and end dates for the sprint. You can also choose to set the sprint as “active” or “closed.”
4. Select the issues that you want to include in the sprint by searching for them, or by dragging them from the backlog onto the sprint.
5. Click on “Create” to create the sprint.

Once the sprint has been created, you will be able to view the sprint on the “Sprints” page, and see the issues that are included in the sprint. You can also update the sprint at any time by clicking on the gear icon and selecting “Edit Sprint” in the drop-down menu.

Additionally, you can also use the board view and move the issues to ‘in-progress’ , ‘done’ etc. You can also see the burndown chart and also plan your sprint from the board view.

It’s also worth to mention, if you are using Scrum framework, you can also plan a sprint using backlog grooming, where you estimate stories points, prioritize and then plan for the sprint.

Also, check Permanent WFH Software Testing Jobs

What is story points in Jira?

In Jira, a story point is a unit of measure used to estimate the effort required to complete a user story. Story points are typically used in agile software development, and are part of the process of estimation in a technique called “planning poker.”

During planning poker, a team of developers, designers, and product managers will come together to estimate the effort required to complete a user story. Each team member will provide an estimate in the form of a story point value, which represents the relative complexity of the user story. The goal is to arrive at a consensus estimate that everyone agrees on.

Story points are typically represented using the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, etc.) or a similar sequence of numbers, which helps to account for the fact that it can be difficult to estimate the effort required to complete a task when it is highly complex or uncertain. The idea is that a user story that is estimated at 8 story points is roughly twice as complex as one estimated at 5 story points.

Story points are used to help teams estimate the effort required to complete a set of user stories and plan their sprints, iterations or project. They are intended to provide a consistent and objective way of estimating the complexity of work.

It is worth to notice that Story points are a relative measure and does not reflect any real measure of time, it will depend on the complexity, uncertainty and team productivity as well.

Also, check Software Testing Study Materials

How to create epic in Jira?

In Jira, an epic is a high-level issue that represents a large body of work. It is often used to group related user stories together, and can be used to track the progress of that work as a whole. Here’s a basic overview of how to create an epic in Jira:

1. Log in to your Jira instance, and navigate to the project where you want to create the epic.
2. In the top-left corner of the page, click on the “Create” button.
3. From the “Create” menu, select “Epic.”
4. A form will open, where you can add details about your epic. Here you can fill in the summary field which will be the title for your epic, the description, and any additional fields that are relevant to your project.
5. Choose the epic’s priority, which will affect its place in the backlog, and also if you are using any kind of workflow, you can assign it to a specific status.
6. Select the Epic Link field and you can link the epic to a user story, issue or any other issue type that is relevant to this epic, this is a good practice to keep track of your work and progress on the epic.
7. Press the “Create” button at the bottom of the form to create the epic.
8. Once the epic is created, you can view it on the “Epics” tab in the left sidebar of the project page, you also can view all linked user stories, issues or tasks, and track the progress of the epic.

You can also use different features such as:

• Assign the epic to a user or a team
• Add labels to the epic
• Add comments and attachments to the epic
• Track the time spent on the epic
• And many other depending on your Jira configuration.

In general creating an epic in Jira is quite straightforward process, however, it could be a little bit different depending on your specific Jira instance or configuration, your organization might have created custom fields, statuses or specific way of using the epics.

Also, check our Software Testing QuestionHub

How to create subtask in Jira?

In Jira, a subtask is a type of issue that is used to break down a larger task into smaller, more manageable pieces of work. Subtasks can be used to track the progress of individual components of a larger task, and can be assigned to different team members for completion. Here’s a basic overview of how to create a subtask in Jira:

1. Log in to your Jira instance, and navigate to the project where you want to create the subtask.
2. Locate the parent task or issue you want to create a subtask for, and click on its title to open it.
3. In the top-right corner of the issue detail view, click on the “More” button, and then select “Create Sub-Task” from the dropdown menu.
4. A form will open, where you can add details about your subtask. Here you can fill in the summary field which will be the title for your subtask, the description, and any additional fields that are relevant to your project.
5. Choose the subtask’s priority, which will affect its place in the backlog, and also if you are using any kind of workflow, you can assign it to a specific status.
6. Press the “Create” button at the bottom of the form to create the subtask.
7. Once the subtask is created, it will be linked to its parent task and you can view it on the parent task view, you also can view all linked subtasks, and track the progress of the parent task.
8. You can also link the subtask with other issues, or subtasks, by using the “Link” feature.

You can also use different features such as:

• Assign the subtask to a user or a team
• Add labels to the subtask
• Add comments and attachments to the subtask
• Track the time spent on the subtask
• And many other depending on your Jira configuration.

As I mentioned before, creating subtask in Jira is a straightforward process, however, it could be different depending on your specific Jira instance or configuration, your organization might have created custom fields, statuses or specific way of using the subtasks.

Also, check our Blog to surf in Software Testing

How to raise defect in Jira?

In Jira, a defect is an issue that represents a problem or error in the software that needs to be addressed. Defects can be raised by developers, testers, or users, and are typically used to track the progress of fixing bugs and other issues in the software. Here’s a basic overview of how to raise a defect in Jira:

1. Log in to your Jira instance, and navigate to the project where you want to raise the defect.
2. In the top-left corner of the page, click on the “Create” button.
3. From the “Create” menu, select “Bug” or “Defect”, depending on the issue type used in your Jira instance.
4. A form will open, where you can add details about your defect. Here you can fill in the summary field which will be the title for your defect, the description, and any additional fields that are relevant to your project.
5. Fill out any additional fields that are specific to your project, like the Environment, Severity, etc.
6. Choose the defect’s priority, which will affect its place in the backlog, and also if you are using any kind of workflow, you can assign it to a specific status.
7. Press the “Create” button at the bottom of the form to raise the defect.
8. Once the defect is raised, it will be in the backlog, and you can view it in the “Bugs” or “Defects” tab in the left sidebar of the project page, and also you can assign it to a team member to fix it.

Also, Join our Software Testing Community it’s FREE

You can also use different features such as:

• Assign the defect to a user or a team
• Add labels to the defect
• Add comments and attachments to the defect
• Track the time spent on the defect
• And many other depending on your Jira configuration.

It is also important to say that you can use different ways of creating a defect, such as creating it from a test case, or creating it from another issue, using the “Convert to” feature.

As with epics and subtasks, raising a defect in Jira is a straightforward process, however, it could be different depending on your specific Jira instance or configuration, your organization might have created custom fields, statuses or specific way of using the defects.

Social SitesLinksFollow us on Google NewsClick HereJoin our Whatsapp CommunityClick HereLike our Facebook PageClick HereJoin Software Testing ForumClick HereFollow us on Instagram PageClick HereJoin our Telegram ChannelClick HereSubscribe to our Youtube ChannelClick HereLinkedInClick HereLinkedIn NewsletterClick HereQuora SpaceClick HereFollow us on MediumClick HereTwitterClick HereOur WebsiteClick Here*** Connect with us ***

What is Jira?

Jira is a project management and issue tracking tool that is widely used in the software development industry. It is developed and maintained by Atlassian, and is designed to help teams plan, track, and release software projects.

Jira provides a wide range of features that are designed to support the needs of software development teams, including:

• Support for agile development methodologies such as Scrum and Kanban
• A customizable workflow that can be tailored to the needs of your team
• A flexible issue tracking system that can be used to track bugs, user stories, tasks, and other types of work
• A built-in backlog that can be used to prioritize work and plan sprints
• A rich set of reporting and analytics tools that can be used to track progress and identify trends
• Integrations with other popular development tools such as Git and Slack

Jira is a web-based tool, so it can be accessed from any device with an internet connection, this allows teams to work together seamlessly and it is available in two main versions: Cloud and Server, the cloud version is hosted on the Atlassian’s servers and is more flexible with a lower cost of entry, while the Server version is an on-premises installation, which has more customizable options, also it requires more technical knowledge to install and maintain.

Jira is a powerful tool, and it can take some time to learn how to use it effectively, but many teams find that the investment is well worth it, as it can help them to streamline their development process and improve their overall productivity.

Also, check Software Testing Interview Questions and Answers

Who can create issue in Jira?

In Jira, issues can be created by any user who has been granted the appropriate permissions by a Jira administrator. These permissions are typically controlled through Jira’s project roles and permissions system.

There are several different built-in roles in Jira, each with its own set of permissions. For example, the “Users” role has very limited permissions, and can only be used to view issues and make comments on them. On the other hand, the “Developers” role has more extensive permissions, including the ability to create and edit issues.

Jira administrators can also create custom roles with custom sets of permissions. This allows for a high degree of flexibility in terms of controlling who can create and work on issues in Jira.

It’s worth noting that, even if a user has the necessary permissions to create issues in Jira, they may still be subject to certain restrictions. For example, an administrator may have set up an issue creation quota, which limits the number of issues that a user can create within a given time period. Additionally, some projects may have specific issue creation guidelines, which users must follow when creating issues.

All in all, the ability to create issues in Jira depends on the user’s role, the project’s settings and global Jira settings.

Also, check Most Important Automation Testing Topics

What is Jira tool?

Jira is a widely-used tool for issue tracking and project management. It is developed by Atlassian, a company that specializes in software for teams. Jira is designed to help teams plan, track, and release software, but it can also be used to track and manage issues in other areas, such as IT operations, customer service, and human resources.

Jira is built on the principle of “issues,” which can represent anything from a bug or defect in software, to a task or user story, to a helpdesk request. Users can create, assign, and track issues, as well as set priorities and due dates, and track progress over time.

Jira also includes several other features that help teams work together effectively:

• Dashboards and reports: Users can create custom dashboards and reports to monitor progress on different aspects of a project, such as the number of open issues, the number of issues resolved per day, and the distribution of issues across different components or teams.
• Customizable workflows: Jira allows teams to create custom workflows to match their specific process and needs, this can help in guiding the issues through different statuses and the different team members or departments.
• Integrated development tools: Jira can be integrated with other development tools like Git, Jenkins, and Confluence. This allows developers to link issues with their corresponding code changes and test results, which makes it easier to track progress and diagnose problems.

Jira is widely used in many different industries and organizations, and has a large user community. it also available in both Cloud and Server versions, which you can host on your own server or in the cloud.

Jira is widely used by software development teams, but it can also be used in any other organization with a need to track and manage work items.

• Save

JIRA — Software Testing QuestionHub #12 1

Also, check Most Important Manual Testing Topics

How to write test cases in Jira?

Writing test cases in Jira is a two-step process: first, you create an issue for each test case, and then you add the details of the test case to that issue. Here is an overview of the steps involved:

1. Create a new issue: You can create a new issue by clicking on the “Create” button in the top-right corner of the Jira interface. Depending on your Jira configuration, you may need to select a project and issue type (such as “Test Case”) before creating the issue.
2. Add test case details: Once the issue is created, you can add the details of the test case to it. This typically includes the following information:

• Test case name: A short, descriptive name for the test case.
• Description: A more detailed description of the test case, including the steps to be followed, the expected outcome, and any relevant information about the test environment or data.
• Test Steps: The steps to reproduce the test case, including the inputs and expected outcomes.
• Test Data: Any data that is needed to run the test case, such as test account credentials or test files.

1. Assign the test case: Assign the test case to someone who will be responsible for running the test and marking it as pass/fail.
2. Plan the test case execution: Add the test case to a sprint or test plan, which will let you track the progress of testing and make it easier to report the test results.
3. Run the test: Once the test case is planned and assigned, it can be executed by the person who has been assigned to it.
4. Report the test results: After the test is executed, the person who ran the test will update the issue with the test results (pass/fail) and any relevant comments.

It’s worth noting that these steps may vary depending on the specific version of Jira and the plugins you have installed, as well as the custom fields and workflows that your team is using. Some organizations use third party test management tools that integrate with Jira to automate the test management process and generate reports.

Also, Jira provides testing tools like Xray that help teams to create, execute and report on their test cases within Jira. This plugin can be used in conjuction with Jira’s Agile boards, it provides several functionalities, like creating Test Plans, Creating and Managing Test Executions and Reports.

Frequently Asked Questions on Jira

1. Q: How do I create a new issue in Jira?
2. A: To create a new issue in Jira, click on the “Create” button in the top-right corner of the Jira interface. Select the project and issue type (such as “Bug,” “Task,” or “Story”), and then fill in the fields with the relevant information about the issue. Once you have completed the required fields, click on the “Create” button to create the issue.
3. Q: How do I assign an issue to someone in Jira?
4. A: To assign an issue to someone in Jira, click on the issue and select “Assign” from the “More” drop-down menu. Select the person you want to assign the issue to, and then click on the “Assign” button to assign the issue. You can also assign the issue by editing the issue and selecting the assignee in the “Assignee” field.
5. Q: How do I track the progress of an issue in Jira?
6. A: To track the progress of an issue in Jira, you can use several different features, including the issue’s status, the issue’s history, and Jira’s built-in reports and dashboards. You can also use the Agile boards to track the progress of issues as they move through different stages of the workflow.
7. Q: How do I change the status of an issue in Jira?
8. A: To change the status of an issue in Jira, click on the issue and select “Edit” from the “More” drop-down menu. Select the new status from the “Status” field, and then click on the “Update” button to save the changes. You can also change the status by transitioning the issue through the custom workflow defined for the project.
9. Q: How do I link issues together in Jira?
10. A: To link issues together in Jira, click on the issue you want to link and select “Link” from the “More” drop-down menu. Select the issue type you want to link to, and then search for the issue by entering its key or summary. Once you have found the issue you want to link to, click on the “Link” button to link the two issues together.
11. Q: How do I create a new project in Jira?
12. A: To create a new project in Jira, you will need to be a Jira administrator. To create a new project, go to the Project settings, then select the “Projects” link, and then click on the “Create Project” button.