Bill Sheboy Expert

Hi @Brian Swackhamer -- Welcome to the Atlassian Community! What would you do with those specific counts if you had them? Would having the values as a graphic over time work for your need? If so, please consider if Jira's version of the Cumulative Flow Diagram (CFD) report would work. You may adjust to just show the…

Hi Dave, Sorry, I wasn't recommending a specific product with my comment...I rarely do so :^) Instead I was more generically noting tools which can show a work breakdown structure (WBS) graphically. I'll try to be more precise in the future. Thanks! Best regards, Bill

Hi @djemani yannick ulrich -- Welcome to the Atlassian Community! Short answer is that you cannot do this with out-of-the-box Jira Cloud. Longer answer: * There is no built-in visualization of issue structure, like your diagram. And the JQL searches are not a SQL, so you cannot work downward in the link tree with…

Hi @Gregory Gadow -- Welcome to the Atlassian Community! It appears that feature is in the backlog and not yet available: https://codebarrel.atlassian.net/browse/AUT-2009 Best regards, Bill

Hi @lisa Agreeing with Jack, an alternative many use rather than Delete is to create an Abandoned indicator (custom field, status, label, etc.) Mark things as abandoned rather than delete them, and then update board filters to not show abandoned issues. Best regards, Bill

Hi @Aurélien Tricoire -- Welcome to the Atlassian Community! To submit a support request, your site admin will need to do that using the link that @Danyal Iqbal provided. Best regards, Bill

Hi @Amber Arguijo -- Welcome to the Atlassian Community! As you note, with automation rules there is no way yet to access the component lead from the issue smart value, and so do the assignment. Here are the suggestions to support that: https://codebarrel.atlassian.net/browse/AUT-123…

Hi @Erin Blomert Without seeing details of your rule that is failing, I offer two suggestions: 1) If this is using a Created Issue trigger, there could be a timing issue with data availability. Those can sometimes be addressed with a Re-fetch action. The "could not find configured field" message is puzzling though, so...…

Hi @mirunadriana Thanks for the image of the rule and for your explanation. Please try using this to access only the most recent comment: {{issue.comments.last.body}} And, I recommend that you force the values to a specific case, such as lower, to ensure no typos cause mismatches: {{issue.comments.last.body.toLowerCase}}…

Hi @Ragni Jayanthi -- Welcome to the Atlassian Community! JQL is not a SQL, so the syntax you noted cannot work with out of the box Jira: ..."Epic Link" in (project = ABC AND labels = XYZ) To do what you ask with out-of-the-box Jira, you would need to find the epics first, and then create your own CSV list to find the…

Thanks for clarifying, Carlo. No doubt some marketplace vendors will soon reply to your question with suggested solutions. ;^) For automation ideas, here are some sources to get you started: * https://community.atlassian.com/t5/Automation-articles/Jira-Automation-all-the-resources-you-need-in-one-page/ba-p/1388465 *…

Hi @Carlo Lynch Short answer: not with out of the box Jira. Longer answer: * What problem are you trying to solve? * You note the team keeps the issue in a status and marks it as flagged when "paused". That usually means it is still in progress in that status and so any cycle time would include working and non-working…

Hi @abakunov -- Welcome to the Atlassian Community! How do you know an epic is approaching the end? For example, by the due date? If so, you could use Automation for Jira to create a rule to notify you. For example: * Trigger: scheduled rule once per day * Action: lookup issues with JQL for Epics with Due Date overdue or…

Hi @mirunadriana When asking a question about automation rules, it can help to post an image of the rule. That gives the community some context to go with your explanation/question. I suggest that you map out the flow/scenarios you expect could happen with the messaging. (Perhaps with a state transition diagram.) Once you…

John, I am glad to hear that worked for you. If that math results seem unexpected, consider logging the values to see what is up: numerator and denominator. I believe asPercentage rounds (not truncates) so the input values may be the factor.

Hi, Nick. To confirm: is this a Classic or Next-Gen project? Looking at your rule trigger, any issue can trigger that and then try to branch on the Parent. The extra condition ensures your rule bails out (or continues) as expected as soon as possible.

Automation rule smart values are often case-sensitive, so please try this for the lookup: {{lookupIssues.Story Points.sum}} Also, try adding some information to the audit log (or add an email send) to dump out the looked up issues: Count: {{lookupIssues.size}} The list: {{#lookupIssues}}{{key}}: {{Story Points}}{{^last}};…

Oops, sorry that I missed your nesting for the epic link check. You could have used {{triggerIssue.epic link}} instead to be what I intended. No limits on edits, only limits on executions for global rules and for a "run-away", where the rule execution get halted due to rapid execution looping.

Hi @[deleted] Please consider adding a condition after the trigger, checking that the issue type is a Sub-Task. Otherwise other issues could attempt to process this rule. You may see that in the example rule I believe you are following from the library:…

Thanks for clarifying, Kat. My work-around may not help roll up the data; you need two pieces of information which are only in the change logs: the status values issue was in and to whom was it assigned during a window of time. Your JQL can list the impacted issues, but it cannot show the information over time. The…

Hi @Kat -- Welcome to the Atlassian Community! I do not believe you can do that with out-of-the-box Jira... Your query can correctly find what you seek, however the gadget only uses the current status value, not any previous value of status (which is stored in the change logs). What problem are you trying to solve with…

Hi @Fisnik Veseli You can do that with automation rules in Jira. Please take a look at this library of example rules and documentation for ideas. https://www.atlassian.com/software/jira/automation-template-library#/label/all/1453…

Hi @Michelle May For out-of-the-box, free Jira there aren't any Gantt dashboard gadgets. A substitute might be the basic roadmap for projects. That uses epic's start and due dates to timeline work. https://www.atlassian.com/software/jira/features/roadmaps?tab=basic Best regards, Bill

Hi @Julia Foden Do you mean preventing a rule from proceeding when an issue transitions to the same status, such as from "In Progress" to "In Progress"? If so, you may add an advanced condition in your rule to detect that * If {{#changelog.status}}{{fromString}}{{/}} * does not equal *…

Thanks for explaining, @RiFa You cannot visualize that with out-of-the-box Jira features. Perhaps there is something in the marketplace to do it. Otherwise you would need to build something by pushing out the logs with webhooks or pulling them with the REST API. As an alternative, you could create an automation rule that…

Hi @ihe It appears that feature idea is in the Code Barrel backlog as a suggested improvement: https://codebarrel.atlassian.net/browse/AUT-940 Until that gets implemented, the REST API approach Alexis noted would work. Here is an article describing how to implement that:…

Hi @RiFa What problem are you trying to solve? And, what level of detail do you need? If you just need counts, you may use Jira's version of the "Cumulative Flow Diagram" to see how many issues where in each status over time. Best regards, Bill

Hi John, I noted that you changed the trigger to be from the story level (after a story point change) rather than scheduled. That probably will work, however please note in your lookup issues JQL, you are testing "Epic Link" = {{issue.key}} That would try to match a story's key as an epic, which cannot work. Instead you…

Hi @Sundaresen Rungasamy I suggest locating some example issues you believe fit into this scenario you have described, and then review their History in the issue view. That will show what changed and who changed it. If you still believe there is a problem where the issues did not move to the next sprint as expected, please…

Hi @john_howard -- Welcome to the Atlassian Community! You could do this by adding custom fields to your epic and updating them with a scheduled automation rule. Maybe something like this: * Trigger: scheduled with JQL to check just the epics that are not done/completed * Action: lookup issues with JQL for issues in the…