Bill Sheboy Expert

Thanks for clarifying, Nicole! The CFD will show you the count of issues...in a status/column...at a point in time. It helps to see issues with flow in your team's value stream. It will not show the amount of time spent in a column, although you can infer that reading the report. To see information about the amount of time…

Hi @Emily Bleything One way to do this with automation is to use the Lookup Issues action. In that case, you would change your scheduled trigger to just be the schedule (not the JQL). For example: * trigger: scheduled (no JQL) * action: lookup issues using your JQL * action: send the email One advantage of this approach is…

Hi @Nicole Dais -- Welcome to the Atlassian Community! What do you mean by "category"? If you mean the columns/statuses for a team's board, you may want review Jira's interpretation of a Cumulative Flow Diagram (CFD). This shows the count of issues in a particular status over time. Please look here for information about…

Hi @Nithya Ananda FYI, that I am using cloud version and not server/data center. That being noted... I do not believe there is a way to do this yet. Even from site admin functions the listing appears limited to me. There are open suggestions to improve export, REST API access, and other history management for the audit…

Thanks for the reminder, Darryl. __Bill

Hi @Christopher -- Welcome to the Atlassian Community! Have you tried to match on the {{version.id}} value instead with JQL of project = myProject AND fixVersion IN ( {{version.id}} ) If that does not help, please post an image of your rule and of the audit log from an execution that does not work as expected. Thanks! Kind…

Hi @Nick Jennings -- Welcome to the Atlassian Community! I can think of a few ways to solve this, and the simplest may be to turn this problem inside-out: create an annually scheduled rule which creates all the PM tasks at one time, quarterly and annual. You do not state why you are waiting for issue transition to create…

Yes, I understand. Then you will need 2 rules to keep these fields in synchronization: * The rule I provided above, and * A second and opposite rule, which detects a change to Start Date in one sub-task in order to update the Due Date in the other. You should be able to create that by copying and adjusting the first rule.…

Thanks for your thoughts, @sladey Please note I was not stating teams are forced to change, and rather that they may choose to abandon/alter their working norms when a tool cannot support them as it may be more cumbersome to use multiple tools to continue those norms. I was instead asking the frequency of this symptom when…

Thanks for that information! Okay, the isEquals() function returns true or false, and not a date. The key here is how to find the sub-task that you want to update and to give that a date field. Let's assume there is one-and-only-one Produção sub-task with the same parent as the Cadastro sub-task. If so, it seems like what…

Hi @Douglas Oliveira You cannot reference the sub-tasks as you have noted in smart values; each is its own issue, and I expect you will need to use some branching and/or created variables to do this in a condition. Please post an image of your rule as that will provide some context for the community to offer more specific…

Hi @[deleted] In my experience, there aren't "best practices" for such a use case, as teams are different in what they mean by their story point sizing and velocity. For example: * do your sizes reflect effort, complexity, uncertainty, etc. or some combination of these characteristics? * some things are complex to…

Hi @Ency -- Welcome to the Atlassian Community! I am a bit confused by your question as you are mentioning both email and the REST API...both can be used to create Jira issues: * Your site admin could set up an email handler to consume emails and create issues * Any user with access to a project is able to call the REST…

Hi @Marieke Cozijnsen Yes, and...to what Alex notes: Here is a suggestion to make the position of those date fields configurable/pinned, and you may watch/vote for it to see progress: https://jira.atlassian.com/browse/JRACLOUD-70098 Kind regards, Bill

Hi @[deleted] As Nic notes, this behavior appears to be by-design in Jira. A few things you could try to help mitigate this behavior are: * Try not to re-open a task completed in a prior sprint. When an issue needs re-work, treat that as a brand new work item, and link the new issue to the original for visibility/tracking.…

Hi @Ross Musselman I just saw your posting while searching for something, and I wondered if you solved this one yet. If not, have you taken a look at automation for Jira rules? You should be able to do both things with automation rules. Kind regard, Bill

Hi @Sanket Salvi Yes, and...to Alex's suggestions: When you need something specific like this (the last 2 sprints) and you do not want to change the filters manually, you have a limited number of options: * Investigate marketplace addon apps for JQL to see if they can dynamically detect the prior closed sprints *…

Hi @Timothy Fischer -- Welcome to the Atlassian Community! Hmmm...I just tried it and it worked for me. Of note: * When called without parameters, you get 00-49. The next startAt value would be 50. * I believe you can only get back 50 with this call, no matter what you pass to maxResults So please try the following to see…

Hi @JJ Are you using a specific time in status app from the marketplace? If so, you may want to both name the app and check the vendor's documentation to see what is possible. If instead you are noting the Jira built-in Average Time In Status dashboard gadget, I suspect that the time will remain unchanged for unchanged…

Hi @Douglas Oliveira What is the relationship in Jira between these sub-tasks? For example, do they have the same parent, are the linked, etc.? * If this is a one-time change, and these are two unrelated sub-tasks, you could directly edit those fields using the UI * If instead you need this change/edit often and there is a…

Hi @Alex Koxaras -Relational- Sorry, as I am not using JSM. And when I check for documentation on its HTML parsing I didn't see anything beyond what @Kian Stack Mumo Systems already noted. Kind regards, Bill

Hi @soriyo -- Welcome to the Atlassian Community! Would you please clarify what you mean by "category" and perhaps post an image of your board settings? I believe that status category values are hard-coded into Jira Cloud with three values possible: to do, in progress and done. Kind regards, Bill

Hi @Evan Gilner When you note "the newer Jira Automation doesn't support field modification at all currently", what do you mean? Is there a specific field that you are unable to edit with Automation for Jira? Kind regards, Bill

Hi @Danut M _StonikByte_ Thanks for the information! Regarding the "ideal burndown" values, is that always a straight line on this chart, or is it segmented to account for changes in scope over time (which then change the end-point forecast)? Kind regards, Bill

If you have implemented "on hold" as a status, you are correct: you can decide if that value is or is not included. You may want to consider doing both: measure without "on hold" to see the time to do-work and with "on hold" to see its impact on slowing progress.

Hi @Alex Koxaras -Relational- What is the link to the open ticket which you note? Thanks! Kind regards, Bill

Hi @Rawl Ramnidh -- Welcome to the Atlassian Community! JQL is not a SQL, and so it cannot do a join/query like that. If you need this type of query often, please investigate purchase of marketplace apps which enhance JQL features: https://marketplace.atlassian.com/search If you need this only once: consider exporting your…

Hi @Aman and @Mohamed Adel What is the type of that field? I wonder if splitting the values into a list that the advanced branch can use will help: {{#issue.affectedServices}}{{name}}{{/}} And...how are you updating the components? * If you just use an edit action on the field, it could be overwriting with the last one…

Hi @leewarren Changing a Jira CFD to measure based upon something other than count isn't currently possible and has been suggested as a feature for at least a decade: https://jira.atlassian.com/browse/JSWCLOUD-2785 You do not clarify what problem you are trying to solve, and so why measuring a CFD with story points could…

Hi @DWedekind To be candid, I am using Jira Cloud now and have not used server in years...that being noted: I do not believe there are summary gadgets like that built-in, so you may want to investigate options from the marketplace or consider building your own gadget(s). Kind regards, Bill