Bill Sheboy Expert

Perhaps something like this to access the previous value for : {{#changelog.worklog.timeSpent}}{{from}}{{/}} You can see other examples on that documentation page I sent you.

Hmmm...and thanks! I did not think it worked that way. :^) I suggest that you have two options then: * Create 2 rules (triggered on the different field changes) and copy the action part to each rule * Create 3 rules* 2 rules to catch the triggers for the field changes, and to cause a common condition that you can catch…

Hi @Sigrid Schoepel For the Field Value Changed trigger, have you tried to select multiple fields? That should accomplish what you are asking. https://support.atlassian.com/jira-software-cloud/docs/automation-triggers/#Automationtriggers-Fieldvaluechanged Best regards, Bill

Hi @Sapna Mogili How about this approach: * Make a filter for the epic (s) you care about and save it * Add the pie chart gadget to a dashboard, selecting the filter and use the Statistic Type of Status. * You could create a separate pie chart for each epic, as needed That should work for just one Next-Gen board. If you…

If this works for you, please consider marking this question as answered. That will help others in the community find solutions faster. Thanks!

Hi Holly, Thanks for that update. As you proceed, consider people and teams work in different ways, and so tools that help one group may not help another. Remember that tools like JIRA are just tools; they are not meant to change how a team works but instead support it. Also consider observing and discussing what about…

Hi @Ron Becker Have you tried CHANGED AFTER advanced JQL? Maybe something like: project = myProject AND statusCategory = "In Progress" AND NOT status CHANGED AFTER -30d ORDER BY Key Best regards, Bill

Hi @Matthias , and thank you for the update. __Bill

Hi @Gil Carroll I am assuming you mean the number of issues (or sum of story points) which were committed when the sprint started, and the number/sum which were completed when the sprint finished. If so, the short answer is "no; there is no JQL to directly return this information". JIRA appears to use the issue history to…

Hi @Roberto T -- Welcome to the Atlassian Community! There is no a built-in way to do this with out-of-the-box JIRA. There are marketplace add-ons to do this with query scripting or charting gadgets. For a free solution you could: * Create a JQL filter for your in-progress items, such as the following which would return…

Hi @Monica Morris I am glad to hear that helped you. Reducing zoom also helps when creating a query in Issues and Filters, where the type-ahead search hides most of the screen...even after it matches what you typed! Best regards, Bill

Hi Dan, The Due Date field seems curious, and I got it to work using JSON field editing. Note this smart value does not match the documentation or what you get back if you query with the REST API. You can access the value in Due Date for reading with: {{issue.Due Date}} To write in the field with Edit Issue, I had to use…

Hi @Dan Finn -- Welcome to the Atlassian Community! I believe this one is a case-sensitivity issue: dueDate rather than duedate. And, the "business days" appear to be fixed, as you noted. The only way I have been able to work around this was quite elaborate: * Convert to local time zone. For…

Hi @Christina Simpson You could create a story with sub-tasks and clone it as needed. Or, I believe that there are marketplace add-ons to do this. If you do not want to buy add-ons, you could build this yourself with automation rules. For example: * Create an automation rule with* Manual trigger * Action to create issue…

Hi @Roi Angress Disclaimer that I have not tried this, and... Have you tried using the Work Logged (deleted) trigger, and then using changelog to access the previous value? Please look here for information about changelog use: https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/ Best regards, Bill

Hi @Mark Stahura -- Welcome to the Atlassian Community! When a sprint starts on the button press, it does not change the start/end datetimes. So if those had values earlier than your sprint planning, the changes you note would be included. Please check to see if this is the case which is causing the report to behave as you…

Hi @Becky Kirk In addition to what Stephen suggests... Please consider adding a Condition after the Trigger and before the Branch (For Sub-Tasks) to confirm that the issueType matches what you expect: Story. Best regards, Bill

Hi @Alexandra Wiechers Here is a community post which describes a few ways to change the issue type, including information about using ScriptRunner:…

Hi @Sandhya Paranjpe According to that documentation link I provided from Atlassian, 180 days is the limit from the admin pages. They do not indicate if more history is available via other paths. I did find a suggestion to increase beyond 180 days: Jira audit log retention period needs to be increased…

Thanks for the update and the link to the defect... Unfortunately there isn't one place to look for these issues (or documentation either :^) Some are in the old Code Barrel backlog (AUT) and others are in the public Atlassian Cloud backlog. And neither shows the complete list of open known defects. Hopefully both will…

Hi @Nico F_A_ -- Welcome to the Atlassian Community! I am unclear what the speed report is. Do you mean the Velocity Chart: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/ If so, the answer is "no" as that report shows up to the last seven sprints. Of note, looking further…

Hi @Nizan Freedman There are also two older suggestions to add archiving for components, however the responses from product management seem to indicate they are not planning on adding the feature. Still, you can take a look and vote for them if you are interested in watching their progress:…

Hi @Liviu Meister -- Welcome to the Atlassian Community! I do not believe there is a built-in feature for Classic or Next-Gen projects in JIRA Cloud. There are probably marketplace add-ons which you could purchase. There are several suggestions to add capacity management to JIRA, which you can review and vote for:…

Hi @Sandhya Paranjpe You appear to be asking about the audit logs, and not the individual issue history. Is that correct? If so, the Atlassian documentation indicates these logs are available for 180 days: https://confluence.atlassian.com/cloud/audit-logging-970612562.html You can access them via the admin UI or from the…

Hi, and thanks for the information! When you do not get the expected results with a filter, it can help to start with a simpler filter and progressively add the clauses. In that way you can see where the problem exists. For example... project = CN project = CN AND issuetype = Test project = CN AND issuetype = Test AND…

Hi @Prasanth Kamalakannan -- Welcome to the Atlassian Community! Would you please post your filter/query and how you are managing tests: add-on, issue type, etc.? That will help the community provide you with ideas. Thanks! Best regards, Bill

Hi @Morgan Beaupre -- Welcome to the Atlassian Community! Are you using a Scrum or a Kanban board? I am gonna guess Kanban... The things shown on the board are impacted by the filter and board settings, so you can check there first: * Select the ... at the right side of the board, and select Board Settings * Select…

Hi @Holly You ask about automating the integration between Jira cloud and the Mantis defect management tool. Please consider more specific details about what information you want exchanged between systems, direction, timing, etc. That will help you evaluate approaches, and may help the community offer ideas. In addition to…

Hi @Mariam Grigoryan What do you mean by collective data? For example, do you mean the sum of the story points for the tasks across the projects? One option is to buy an add-on for JQL (JIRA's query language) in the marketplace to support summing. However, you appear to be using the free edition of JIRA cloud, so instead…

Hi @Cameron Taylor I am glad that helped you! __Bill