Bill Sheboy Expert

Hi @Slick Rick -- Welcome to the Atlassian community! In addition to what @Sachin noted, you can use things like CHANGED for some fields (such as status) for points in time. Please look here for more details: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/ Best regards, Bill

Hi @Amy Glass -- Welcome to the Atlassian community! The velocity chart shows the completed work at the end of the sprint. "Complete" is determined for the statuses in the rightmost column for your JIRA scrum board. https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/ From what you…

Hi @Kiran Salgarkar -- Welcome to the Atlassian community! Some things to note and a question to help the community give input... * Classic and Next Gen projects use different statuses, even if they have the same names * Next Gen board filters are simply filters on the project and nothing else (I believe...). So the extra…

Hi @Donata Short-answer: There is no out-of-the box and easy way to do this. But, you could buy or build something. Longer answer: * What will you do with this information, and how often do you need it? If you only need this for one issue, just look at the activity log for the issue and do the math by hand. * Otherwise,…

Oops, my bad. I forgot you cannot nest branches with automation rules. Two possible work-around solutions: 1) I do not have a scripting add-on to test this... If you have something like ScriptRunner you could find the epic for the sub-task and then update it. Use a JQL branch to find the epic. 2) Use two rules, one to find…

Hi @Christophe Noualhat -- Welcome to the Atlassian community! Have you tried something like this: * Trigger: sub-task updated (you may want to make this more specific) * Condition: issue type is sub-task * Branch: for parent* Condition on JQL: issuetype = Epic AND key = {{issue.epic link}} * Action: the action you want to…

Hi @Jason Epel -- Welcome to the Atlassian community! I have found several sources to find this info: * This list of values from Atlassian: https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/ * This one on list values…

Removing my answer as it does not match the problem statement.

Hi, Tom. Yes, I meant it worked when on the board. The behavior appears to be the intended design: * When on the backlog view, the view helps with refinement and selection of work (scrum or Kanban) and so only offers to move issues up/down in backlog and in/out of selection for next work (a sprint for scrum and your first…

Hi @Myron Melnyk -- Welcome to the Atlassian community! To confirm my understanding: * Your team previously used a workflow that ended with Done * Several sprints completed * Your team added more statuses, placing them in the last column on your board * And now the prior sprints' reports are incorrect Is this what you are…

Hi @Ray Nixon Have you tried this smart value: <span>{{initiator.displayName}}</span> Best regards, Bill

Hi @Zach Herriott For the scrum boards, there are two things that make the issues visible: being in the current sprint and satisfying the filter. You are showing two views of the items with your screen shots, so there is something different in the issues or filters. Please consider finding example issues that are different…

Hi @[deleted] If you post more details about your automation rule, that will help the community consider what is happening and offer advice. Something for you to check: are you certain the correct issue is selected transitioning? To diagnose this, please consider: * Review the individual issue's log to see what happened *…

Hi @Tom Hudson Is this a next gen or classic board? I just tried this with my classic Kanban board, and when I was on the board I have the right-click option to "Send to Top of Column". Best regards, Bill

Hi Jason, I was suggesting using Status Category for the condition rather than Status because Status Category is less granular. It only has the values: To Do, In Progress, and Done. Is basically summarizes the many possible values you have for Status. Re-fetch is an action in automation rules. You use it when an issue may…

Hi @Jean-François RIOU The link I sent has the steps to add new custom fields. You can add a field of Date/Time type to meet your needs, or just add a Number field if you want the value in Weeks, Days, or Hours, as you noted. I recommend reading the information before starting the steps. At the bottom of the linked page,…

Hi @Jean-François RIOU What would be the purpose of this new field? You could add a new custom field for what you need, and make it visible on the relevant projects and views. Here is the information on how to do so: https://confluence.atlassian.com/adminjiracloud/create-a-custom-field-991923727.html Best regards, Bill

I added these suggestions to help with that in the future. :^) Validate automation rules before saving https://jira.atlassian.com/browse/JSWCLOUD-20445 https://jira.atlassian.com/browse/JRASERVER-71196

I believe that is missing one brace at the end and has extra parenthesis. Please try: {{now}}

Hi, @Zoryana Bohutska _SaaSJet_ Yes. Using the automation rules you could create a rule with a trigger watching for a specific field change, and then transition to the new status. Best regards, Bill

Hi, Jason. In the case you note about future status changes, consider instead using status category as your check. For logging that doesn't seem to be working, consider adding comments and perhaps re-fetch. You can remove them later once the rules work.

Hi @JasonB3 I haven't seen this before. Have you tried to confirm/isolate the result by inverting your Some Match JQL from status != "Done" to instead use status IN (your valid other values) That would confirm if it is the not-equal test or if there is something else causing it not to return the results you expect. Best…

Hi @Jenn Sherman Your custom field names have embedded spaces. Have you tried either enclosing the names in quotation marks or using using the custom field ID? For example: {{#=}}{{issue."retention benefit"}} + {{issue."growth benefit"}} + {{issue."cost savings"}} - {{issue."dev cost"}}{{/}} UPDATE: please disregard as I…

Hi @Yana Nikolayeva We did the same thing, and we added additional custom fields to track cycle time for various phases of work: dev cycle time, test cycle time, and build cycle time. Three things to watch for when using this technique: rework, cloning, and rule execution order. * When you have rework, decide whether or…

Hi @Samuel Smiles P Unfortunately this isn't built into JIRA (out of the box) in a way to use as you have asked. It is probably only worth solving if you have a lot of sub-tasks. You listed a couple of options that would work: export to Excel, or automation rules. In addition, if you have one of the marketplace JQL…

Hi @Dionei Piazza You may be interested in reading this post on the topic, as it includes some ideas and "spirited conversation". :^) https://community.atlassian.com/t5/Jira-questions/Explicit-DoD-lane-policies-on-Kanban-boards/qaq-p/177540 There are also some links to suggested improvements to add this feature to JIRA.…

Hi @Yair Leiferman Yup, that's a problem. The only work-around I have seen is to reduce your browser zoom quite a bit, set the options and save, and then zoom back up. It is even worse if you turn on the accessibility features for high-DPI monitors; many of the scrollers and type-ahead search features of JIRA are broken…

Yes...you can form a JQL query to get your needed data, and then access it with the REST API. Here is the complete reference list: https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/ Here are some good examples: https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/

Hi @graemejohnson Short answer: This *should* be possible, using Excel and Power Query functions, however... I tried this a couple of months ago without success. There are several how-to articles and free templates on the interwebs to do this. I'll share what worked and did not work for me. Hopefully you will have more…

Short version is that you cannot do exactly what you want with out-of-the-box JIRA. JIRA's JQL is not SQL. It is unlikely that Atlassian will make it so; there are marketplace vendors who have products to fill the gaps in JIRA and JQL. If you want to investigate additional query add-ons, they do appear to have GROUP BY…