Alexey Pavlenko (App Developer) Atlassian Partner

@Gaurav Pardeshi , Cool, glad that it works now. Best regards, Alexey

@Gaurav Pardeshi , Please describe the expected result. Do you really need only epics with the label you specified? resolutiondate >= "2024/06/24" and resolutiondate <= "2024/09/01" should definitely work. If it returns nothing, then you don't have resolved issues for this period. If the query returns an error, the search…

Hi @Gaurav Pardeshi , The correct expression you need to use in your JQL is resolutionDate >= "%PI_START_DATE%" AND resolutionDate =< "%PI_END_DATE%" However, it requires manual maintenance. For an automatic solution, you can use the app I developed - Multi-team Scrum Metrics & Retrospective. Look at the Completed Scope…

Hi @Gaurav Pardeshi , Unfortunately, natively for PI it's impossible to automatically measure: * Flow Velocity * Flow Time * Flow Efficiency * Flow Predictability As for Flow Load, you can use the following expression: statusCategory = "In Progress" For Flow Distribution, Flow Velocity, Flow Load and Flow Predictability…

Hi @Dennis de Laat , Here are a few ways to achieve this:* Navigate to 'Search' -> 'View all issues' -> Switch to 'JQL' view from 'Basic' -> Enter timespent > 0 in the search field. * Go to a project -> Select 'Reports' -> 'Time Tracking Report'. * Utilize third-party applications. With my app, Multi-team Scrum Metrics &…

Hi @Matthew Taylor , I dealt with the same things and from my standpoint, to succeed in portfolio/program delivery, you need to concentrate first of all on the ground things. Some of these are: * Tracking, visualizing and reporting any Scrum or custom JQL metrics of teams across sprints, months, quarters, half-years, or…

Hi @Scott Walter , There are several options to achieve this. * Click on 'seach' -> View all issues -> Choose 'JQL' view instead of Basic -> Enter in the search field: timespent > 0 * Click on a project -> choose 'Reports' -> 'Time Tracking Report'. * 3rd party apps. With the app I have developed - Multi-team Scrum Metrics…

Hi @MinSik Choi , Natively, unfortunately, it's not possible. You can use the app I have developed instead - Multi-team Scrum Metrics & Retrospective. It allows you to cover all your requests if you use sprints. You can track team members by constructing custom JQLs: Screenshot #1 On the Screenshot #1, you can see the…

Hi @[deleted] , Unfortunately, the data you provided is not enough to answer your question definitely. It all depends on how do you track all of these. There is some probability that you will be able to achieve that with JQLs and native JIRA gadgets. If not, and you use sprints, then you can try the app I have developed…

Hi @Learning123 , You can achieve it manually via constructing JQLs issuetype = bug and sprint = %YOUR_SPRINT% issuetype = story and sprint = %YOUR_SPRINT% and adding them to some of the JIRA gadgets, for example, Two Dimensional Filter Statistics or Pie Chart. You will have to constantly update sprint IDs. If you would…

Hi @Riyas Khareem , Did you try the Sprint Report? Or you need to collect the Removed Issues from over 7 sprints? If you need to collect the Removed Issues from over 7 sprints, the only consistent way is to use the JIRA REST API or 3rd party app. The app I have developed - Multi-team Scrum Metrics & Retrospective - has…

Hi @Sorokach, Mark D , Natively, you can get * User story accepted points (Committed) via the Velocity Report * User story throughput via JQL and use some native gadget to visualize it * Average velocity - calculate manually from the Velocity Report * Average User Story Cycle Time - calculate manually from the Cycle Time…

Hi @Daniela Cancino , 1. Your title contradicts to your JQL: project = "POL" AND sprint IN (2, 75, 110, 344, 744, 876, 1008) ORDER BY createdDate DESC This JQL will show all the tickets presented in the sprints.2. Actually, I think your problem is the opposite. Since you are trying to aggregate the story points of all…

Hi @Kaladin Stormblessed , Unfortunately, natively JIRA can't do it. You can manually aggregate this data by exporting data from Issue Navigator to Excel. Or you can use the app I have developed - Multi-team Scrum Metrics & Retrospective. In this case, it will do it automatically for you and provide a lot of additional…

Hi @Liesbeth K_ , If you are open to 3rd party apps and you would like to have visualization of it, then you can use the app I have developed - Multi-team Scrum Metrics & Retrospective. Using custom JQL filters, you can get this view: Best regards, Alexey

Hi @Youssef fawzi , If you use agile frameworks, I wouldn't recommend incentivizing people individually, but rather as a group. If you still would like to keep it the way you described, you can use the app I impemented - Multi-team Scrum Metrics & Retrospective. Using custom JQL filters, you can setup individual metrics,…

Hi @Colleen Stone , Unfortunately, natively JIRA doesn't allow you to get this view for several teams in one place. If you are open to third-party apps, I would suggest using the one I have developed - Multi-team Scrum Metrics & Retrospective. It allows you to track not only the standard metrics but also: 1. Create your…

Hi @Alicia Redden , Please tell me if you tried to create a JQL filter, a dashboard, add the 'Filter Results' gadget, specify the JQL filter you created earlier in the gadget, and choose the columns you mentioned above? Best regards, Alexey

Hi @jodywhite , "Issue added to sprint after start time" - shows only issues added to a sprint after it has started. The Burndown Chart reflects both issues added to a sprint after it has started and estimate change. The metric to use depends on your requirements. It can be useful to track both of them. Best regards, Alexey

@MA , Thank you for the answer. If I understand correctly, you would like now to report based on epics. Since now an epic is a higher entity in your hierarchy than a release. Maybe I am missing something but with the Time Tracking report you can construct reporting based on fixversion (or the absence of it) only. Best…

@Paula Smith Thank you for the response. Do I understand correctly that you would like to see the metrics for over 10 months in 1 gadget, but since there is a limitation of 10 smart filters, you cannot do that? Best regards, Alexey

Hi @Jyoti Singh , Unfortunately, for the graph with this custom approach, you will have to use 3rd party applications. Native JIRA doesn't have this functionality. I recommend the one I have developed - Multi-team Scrum Metrics & Retrospective. It covers your request via custom JQL. For this, you need to find some…

Hi @Paula Smith , Please elaborate a bit on 'only allowing me to do 10 entries'. Where does it come from? Probably provide screenshots to make sure that we are on the same page. Please also let me know if you use sprints and open to 3rd party applications. Probably I can suggest you all in one solution. "I'm struggling…

Hi @Admova , Unfortunately, native JIRA doesn't support this functionality. Even the most custom applications don't support all the functionality you are asking for. If you can't purchase a 3rd party application and you are ok with the manual approach, I would recommend: * Use 3rd party gadget with free HTML editing if…

Hi @assafm , Could you please add several screenshots of the issues you encounter? Unfortunately, I am not sure I completely understand what you are talking about. Thanks. Best regards, Alexey

Hi @Rodrigo Coutinho , Unfortunately, there is no way to do that. The native version of the Velocity Chart is quite limited. The only workaround is to delete the sprint and create a new one. If you use the app I have developed - Multi-team Scrum Metrics & Retrospective, you could just use the Final Scope metric instead of…

@Yatiraj Sharma From my perspective, my filters above still cover your case. You can list all the sprints in JQLs that a PI consists of. Another solution could be to create another custom field to track the history, such as a 'History PI' field. You can maintain it manually or automatically. Best regards, Alexey

Hi @Yatiraj Sharma Did you try the native Sprint Report? Unfortunately, you won't be able to construct Committed Scope and Removed Scope metrics using JQL, since you need to interate over the history of each issue in a sprint. As for the Completed Scope metric, you can construct a JQL in this way Sprint in (%SPRINT_NAME%)…

Hi @Humberto Gomes * In the Issue Navigator (Advanced JQL Search) set up columns you want to be presented in your PDF file. * Export to Word. * In the Word document, save as a PDF file. All this can be automated if you know how to program but not natively in JIRA. Best regards, Alexey

Hi @MA, * Can please a bit elaborate on "If we use EPICs in order not to obscure the time, we will not put any time against the specific epic only show the start and end date."? * What do you mean by 'JIRA template'? * Have you tried using native JIRA gadget - 'Filter Results'? Just in case you aren't aware, you can add…