JIRA – Workload Pie Chart ”; Previous Next A workload pie chart displays a pie chart showing all the issues for a specific project. Let us understand how to use it in JIRA. Generate a Report To generate a report, the user should follow the steps given below. Step 1 − Go to Project → choose the Specific project. Click on the Report icon on the left side of the menu. Go to ‘Others’ section and click on Workload Pie Chart Report as shown in the following screenshot. Step 2 − Select Project or issue filter for which to generate the report. In the Statistic Type, select the field name on which the pie chart will be formed. Select the Time Field to report on as Current Estimate, Original Estimate or Time Spent. The following screenshot shows how to generate a report by providing details. Step 3 − Click on Next to generate the report. The following screenshot shows how the generated report looks like. Print Page Previous Next Advertisements ”;
Category: jira
JIRA – Advanced Search
JIRA – Advanced Search ”; Previous Next Apart from the type of searches explained in the previous chapter, JIRA also has a few advanced search options, which can be performed using the following three ways. Using Field Reference Using Keyword Reference Using Operators Reference These above-mentioned three ways have been explained in detail below. The user should consider the following points while performing any advanced search. Advanced search uses structured queries to search for JIRA issues. Search results displays in the Issue Navigator. Search results can be exported to MS Excel and many other available formats. Save and Subscribe features are available to advanced searches. An advanced search uses the JIRA Query Language known as JQL. A simple query in JQL consists of a field, operator, followed by one or more values or functions. For example, the following simple query will find all issues in the “WFT” project − Project = “WFT” JQL supports SQL like syntax such as ORDER BY, GROUP BY, ISNULL() functions, but JQL is not a Database Query Language. Using Field Reference A field reference means a word that represents the field name in the JIRA issue including the custom fields. The syntax is − <field name> <operators like =,>, <> “values” or “functions” The operator compares the value of the field with value presents at right side such that only true results are retrieved by query. Go to Issues → Search for Issues in the navigator bar. The following screenshot shows how to navigate the Search section. If there is an existing search criterion, click on the New Filter button to reset the criteria. The following screenshot shows how to start with a new criteria − Type the query using the Field, Operator and Values like issueKey = “WFT-107”. There are other fields as well – Affected Version, Assignee, Attachments, Category, Comment, Component, Created, Creator, Description, Due, Environment, etc. As soon as the user starts typing, the auto-complete functionality helps to write in the defined format. The following screenshot shows how to add Field Name criteria using advanced features. Operator selection − The following screenshot shows how to select operators. The next step is to enter the value and then click on the Search symbol. The following screenshot shows how to add values and search. The following screenshot shows the search result based on criteria set. Using Keyword Reference Here, we will understand how to use a keyword reference and what its advantages are A keyword in JQL − joins two or more queries together to form a complex JQL query. alters the logic of one or more queries. alters the logic of operators. has an explicit definition in a JQL query. performs a specific function that defines the results of a JQL query. List of Keywords − AND − ex – status = open AND priority = urgent And assignee = Ashish. OR − ex – duedate < now() or duedate is empty. NOT − ex – not assignee = Ashish . EMPTY − ex – affectedVersion is empty / affectedVersion = empty. NULL − ex – assignee is null. ORDER BY − ex – duedate = empty order by created, priority desc. Similar to field reference, as soon as the user starts typing, the auto-complete functionality helps to get the correct syntax. The following screenshot shows how to add keywords. Click on the Search symbol and it will provide the search results. The following screenshot shows the result based on a criteria set. Using Operators Reference Operators are used to compare values of the left side with the right side, such that only true results display as the search result. List of Operators Equals: = Not Equals: != Greater Than: > Less Than: < Greater Than Equals: => Less than equals: =< IN NOT IN CONTAINS: ~ Does Not contain: ! ~ IS IS NOT WAS WAS IN WAS NOT IN WAS NOT CHANGED Similar to the Field and the Keyword Reference, these operators can also be used to enhance the search results. Print Page Previous Next Advertisements ”;
JIRA – Watch and Vote on Issue ”; Previous Next In this chapter, we will understand how Voting and Watching is done on an issue in JIRA. Voting on an Issue JIRA has a feature called as Vote to provide the opinion on the preference for that issue, whether it is resolved or completed. Admin needs to add permission for users to use this feature. Go to the View Issue page where voting is required. Click Vote for this issue to instantly vote for that issue. The following screenshot shows where Votes field is present at issue detail page − Note − Since the user does not have permission here to vote, the user is not able to view the link beside Votes field. Watching an Issue JIRA has a feature that allows users/stakeholders to keep an eye on the issue, whenever there is any update or changes in that issue. If there is any the issue, it sends notification/emails to those who are listed as watchers for that specific issue. Admin needs to add permission for users to use this feature. Go to the view issue page that the user wants to watch. Click on the “Start Watching this issue” link to be listed as watchers. The following screenshot shows where the Watchers field is present in the Issue Detail page. Now instead of zero watchers, there will be 1 (watcher) displayed along with the link “Stop watching this issue” to delist as watchers. The following screenshot shows the updated number of watchers − The user can click on 1, it allows to add other users as well to the list as watchers. Start typing the user name in the Add watchers box and select from the autocomplete box. The user will be listed as watchers. The following screenshot shows how to add a new watcher by providing the user’s detail. Print Page Previous Next Advertisements ”;
JIRA – Discussion
Discuss JIRA ”; Previous Next JIRA is a project management tool used for issues and bugs tracking system. It is widely used as an issue-tracking tool for all types of testing. This tutorial introduces the readers to the fundamental features, usage, and advantages of JIRA. This tutorial will guide the users on how to utilize this tool to track and report bugs in different applications. Print Page Previous Next Advertisements ”;
JIRA – Search
JIRA – Search ”; Previous Next JIRA has powerful and very efficient search functionalities. A user can search issues across Projects, Versions and Components using various search types. JIRA allows saving the search criteria to utilize next time as filters; even these filters can be shared by others as well. Types of Searching Options JIRA has a couple of fundamental ways to search issues. The most important ones are as follows. Basic Search Quick Search Let us now understand both of these search types in detail. Basic Search Basic Search in JIRA is a user-friendly interface that can be used easily to find out the issues. It uses the JQL queries in the backend. To do a basic search in JIRA, the user has to follow the steps given below. Step 1 − Navigate to issues → Search Issues. The following screenshot shows how to access the Search for Issues feature − Step 2 − A search page displays. If it has any existing Search criteria, then click on the New Filter to reset it. The following screenshot shows how to define a new search criteria. Step 3 − Set the search criteria against different fields like Project, Type, Status and Assigned. Then click on More and select any field to search with additional fields. The following screenshot shows what all criteria’s can be set to search issues. Step 4 − If the user wants to search against any specific text, keywords, start typing in the Contains text box. The following screenshot shows how to search specific text in issues. Step 5 − A user can use wildcards or operators in all text based fields to search specific strings. For example − Single character wildcard – te?t Multiple characters wildcard – win* Boolean operators – “atlassian jira” || confluence Based on different search criteria, the following result is displayed. The following screenshot shows the list of searched issues. How to Save a Search To save the searched criteria, the user should follow the steps given below. Step 1 − Click on Save As at the top of the page. The following screenshot shows how to save the search criteria for future use. Step 2 − Type the filter name and click on Submit. The following screenshot shows how to provide a name of new search criteria before saving. Step 3 − A Filter will appear on the left side of the Search Page under the Favourite filters and it will have a few options like – Rename, Delete, Copy and Remove from Favourites. The following screenshot shows the saved search criteria and the available actions to perform. Quick Search The quick search is the fastest way to define search criteria. It is a text box where the user enters the key, text or anything and it starts searching for the exact matches in the current project and provides the result. The Quick Search box is available on the top right hand corner of the navigator. The following screenshot shows how to access the Quick Search feature. Smart Querying The quick search option performs smart searches with minimal typing. It recognizes the following word and gives out several options to the user to choose. my − This word searches issues assigned to the logged-in user. The following screenshot shows different smart querying in a quick search. Some of the most commonly used smart querying options are as follows − r:me − Finds issues reported by the logged-in user. r:abc − Finds issues reported by user – abc. r:none − Finds issues with no reporter. <project name> or <project key> − Finds issues within the given project name or finds issues having the same project key. Overdue − Finds issues those are overdue before today. Created:, updated:, due: − These smart searches finds issues with Created, Updated, or Due Date using the prefixes created:, updated:, or due:, respectively. For the date range, use today, tomorrow, yesterday, a single date range (e.g. ”-1w”), or two date ranges (e.g. ”-1w,1w”). Date ranges cannot have spaces between them. Valid date/time abbreviations are: ”w” (week), ”d” (day), ”h” (hour), ”m” (minute). C: − Finds issues with a particular component. V: − Finds issues with a particular version. Ff: − Finds issues with a Fixed For version. * − Wildcard can be utilized with any of the above queries to find issues. Print Page Previous Next Advertisements ”;
JIRA – Linking Issues
JIRA – Linking Issues ”; Previous Next This feature is very useful when two issues have some type of a dependency on each other as if they are duplicates or relate to each other, upstream downstream dependency or blocking issues. Create a Link to Another Issue For creating a link to another issue, the user has to navigate to the issue and click on the View Issue Page. After that, click More → Link to display link dialogue page. The following screenshot shows how to access Link feature − Select JIRA Issue item in the left side of the dialogue and select “This issue” field from the dropdown list. The following screenshot shows how to link an issue by providing the details. The next step is to select/search issue. The following screenshot shows how to add an issue as a link in another issue. Add the comment; it is optional and then Click on Link. The View Issue page shows up and the user can go down and verify whether the linked issue is displayed or not under the Section Issue links. The following screenshot shows how to view linked issue in parent issue − Deleting a Link To delete a link, a user should go to the View Issue page and to that issue which contains the links. Scroll down and go to Issue Links section. Hover the mouse over the link that should be deleted and then click on the Delete icon. The following screenshot shows how to delete a link − A confirmation pop-up will display; click on the Delete button. The following screenshot shows the confirmation pop-up for deletion. Print Page Previous Next Advertisements ”;
JIRA – Useful Resources
JIRA – Useful Resources ”; Previous Next The following resources contain additional information on JIRA. Please use them to get more in-depth knowledge on this topic. Useful Video Courses AWS CodePipeline: DevOps CI/CD Masterclass 40 Lectures 5.5 hours Syed Raza More Detail AWS DevOps All-in-One Training Most Popular 155 Lectures 20.5 hours Syed Raza More Detail Introduction on Jira and Confluence 6 Lectures 5 hours Manu Mitra More Detail Atlassian Jira and Scrum Fundamentals for Beginners Best Seller 21 Lectures 1.5 hours Vlajko Knezic More Detail Business analysis & Scrum with JIRA for Software development Best Seller 84 Lectures 16.5 hours Akhilendra Pratap Singh More Detail Maîtriser Scrum et réussir sa certification Scrum Master 38 Lectures 3 hours Eloundou Celestin Placide More Detail Print Page Previous Next Advertisements ”;
JIRA – Created vs Resolved Issues ”; Previous Next It displays the number of created issues versus resolved issues over a given time-period. It helps to understand whether the overall backlog is moving towards resolution or not. Generate a Report To generate a report, the user should follow the steps given below. Step 1 − Go to Project → choose a specific project. Click on the Report icon on the left side of the menu. Go to Issue Analysis and click on Created Vs Resolved Issues Report. The following screenshot shows how to access the Created Vs Resolved issues report − Step 2 − Select the Project or the issue filter for which the report has to be generated. Select the time-period to see reports like Daily, Weekly, Monthly, Quarterly, Annually, etc., available in the dropdown box. Enter the number of days in the Days Previously field to show in the graph. Select Yes or No for Cumulative totals. Select Display Versions as All Versions from the dropdown list. The following screenshot shows how to generate report by selecting different available fields. Step 3 − Click on Next to generate the reports. The following screenshot shows how the generated report looks like. The created issues are displayed in red, while the resolved issues are in green color. Print Page Previous Next Advertisements ”;
JIRA – Reports
JIRA – Reports ”; Previous Next JIRA provides different types of reports within a project. It helps to analyze the Progress, Issues, Showstoppers and Timeliness of any Project. It also helps to analyze the resource utilization as well. How to Access Reports To access reports in JIRA, the user should go to Project → choose Specific project. The following screenshot shows how to navigate to a specific project. Click on the Reports icon on the left side of the page. It will display all the reports supported by JIRA. The following screenshot shows how to access the Report section. When the user clicks on Switch report, it will display the list of reports. The following screenshot shows list of reports available for quick switch. Type of Reports JIRA has categorized reports in four levels, which are − Agile Issue Analysis Forecast & Management Others Let us now discuss the features of the above-mentioned report categories in detail. Agile Following are the list of features of Agile Reports. Burn down Chart − Track the total work remaining, also whether sprint is achieving the project goal or not. Sprint Chart − Track the work completed or pushed back to the backlog in each sprint. Velocity Chart − Track the amount of work completed from sprint to sprint. Cumulative Flow Diagram − Shows the statuses of issues over time. It helps to identify high-risk issues or unresolved important issues. Version Report − Track the projected release date for a version. Epic Report − Shows the progress towards completing an epic over a given time. Control Chart − Shows the cycle time for the product, its version or the sprint. It helps to identify whether data from the current process can be used to determine future performance. Epic Burn Down − Track the projected number of sprints required to complete the epic. Release Burn Down − Track the projected release date for a version. It helps to monitor whether the version will release on time, so mandatory action can be taken if work is falling behind. Issue Analysis Following are the list of features of Issue Analysis. Average Age Report − Displays the average age in days of unresolved issues. Created Vs Resolved Issue Report − Display the number of issues created vs the number of issues resolved in given period. Pie chart Report − Shows a pie chart of issues for a project grouped by a specified field. Recently Created Issue Report − Shows the number of issues created over a time-period for a project and how many of those were resolved. Resolution Time Report − Displays the average time taken to resolve issues. Single Level Group by Report − .It helps to group the search results by a field and see the overall status of each group. Time since Issues Report − It helps to track how many issues were created, updated, resolved, etc., over a time-period. Forecast & Management Following are the list of features of Forecast and Management type of reports. Time Tracking Report − Shows the original and current time estimates for issues in the current project. It can help to determine whether work is on track for those issues. User Workload Report − Shows the time estimates for all unresolved issues assigned to a user across projects. It helps to understand how much a user is occupied, whether overburdened or has less work. Version Workload Report − Displays how much outstanding work is remaining per user and per issue. It helps to understand the remaining work of a version. In addition to these, there are other types of reports that generally have a pie chart in them, which we will discuss in detail in the subsequent chapters. Print Page Previous Next Advertisements ”;
JIRA – Screens
JIRA – Screens ”; Previous Next View Screen It is the arrangement and representation of fields to display in UI whenever a new issue is created or existing issues are modified and issue transitioned through one status to another. If a user logs in as Admin and navigate to Settings → Issues → Screens, he will be able to see all the available screens. The following screenshot shows the available screen for different projects. By clicking on configure, the user will be able to see all the available fields with this screen. Whereas, in the organized/arranged way of order, it will display at the UI. The following screenshot shows how to configure the screen fields. Screen Schemes Screen schemes provides an option to choose fields, which should display when a particular issue type is selected. A screen scheme is mapped with issue type using the Issue Type Screen Scheme. It can be associated with one or more project. A screen scheme can be deleted only when it is not used by any Issue Type screen scheme. The user can add a new screen scheme by clicking on the Add Screen Scheme button. The following screenshot shows the different screen schemes available for the listed projects. Provide all details and the click on the ADD button. The following screenshot shows how to add a new screen scheme. Print Page Previous Next Advertisements ”;