Bill Sheboy Expert

Hi @Haridev Sajikumar -- Welcome to the Atlassian Community! It is not possible to import the change history as that is data managed by Jira. However, if you instead moved the issues from one project to another, the issue history is preserved. Best regards, Bill

Frances, sorry as I do not know what else to suggest. I checked and there are no open defects like this in the public backlog for Next-Gen projects. If you weren't on the free license I would suggest submitting a defect to Atlassian Support. Perhaps someone else in the community who has seen this symptom will comment to…

Thanks for this information about the evolving features. With this and other changes, it will be interesting to see how Classic (company-managed projects) and Next-Gen (team-managed projects) feature sets converge and diverge... Perhaps moving more toward a feature inheritance/override model like in competitor products.…

Thanks for that information. I was asking about the ones showing as in progress still on that report. If you look at the history for them did any move to done, back to in progress, and then forward to done again?

It is {{issue.sprint}} singular. For closure detection, you may check {{issue.sprint.state}} for "closed" Or, you may use JQL: sprint IN closedSprints()

@Dave -- Thanks for clarifying that for me. Curious design choice and I could see that difference causing confusion for teams moving from Standard to Premium licensing. __Bill

Thanks, @Hunter1428 Is there any text missing from the Description in the email, or is it otherwise complete? Have you tried {{issue.description}} removing the fields prefix to see how that impacts the formatting?

Hi @fmak -- Welcome to the Atlassian Community! Unfortunately you cannot perform that query with out of the box Jira Cloud. Your options to solve this depend upon how frequently you need this solved: * Need this often: consider purchasing a JQL add-on from the marketplace to enhance searches * Need this infrequently... a)…

Hi @lindy I am curious about what problem you are trying to solve. It would seem those issues in close, cancelled, and done were assigned to someone when they became "resolved". Why unassign them later, essentially losing the history of who worked on them? Thanks! Best regards, Bill

Hi @Ana-Rita Silva Would you please post an image of the rule(s) you have tried? That will help the community give you ideas. Of note: if you allow the automation rule to create the sub-tasks rather than from cloning, the fields could be copied from the parent task when created. For example: * Trigger: issue created *…

Thanks for that information. To confirm, you are noting the details shown on a NextGen project burndown chart, correct? And, for the issue you noted, did any of them move to done during the sprint, and perhaps move back into progress?

Hi! Here are the suggestions and defects around PR triggers for automation in the public backlog. You may watch/vote for them to see progress.…

Thanks for that information, Rebekah! There are table structures and other gadgets in Confluence which help quite a bit. Sadly there is no super-fancy reporting engine like in competitor products (without marketplace add-ons :^) Please take a look at this tutorial and tips guide to see how that matches up with your needs:…

Hi @Chris Buzon Create Variable helps a bit, and you can do this without one. Please adjust the status names to match your project. * Trigger: transitioned to Done * Condition: has a fixVersion * Action: LookupIssues JQL fixVersion = {{triggerIssue.fixVersion}} and status != Done * Advanced Compare Condition: when…

Hi @Frances Moncrief -- Welcome to the Atlassian Community! Would you please post an image of the chart showing what you describe? That will help the community to provide you ideas. Thanks! Best regards, Bill

Hi, @shar.pentecost ! If you see a different behavior happening after some sprints complete, I recommend you post back here or ask your site admin to submit a defect to Atlassian to investigate: https://support.atlassian.com/contact/#/ Thanks!

Hi @shar.pentecost -- Welcome to the Atlassian Community! I believe what that chart calls "committed" is the work which was planned for the sprint when the sprint started, whatever the source: newly started or carry-over. Best regards, Bill

Hi @Tibor Kocik -- Welcome to the Atlassian Community! For a question like this, you may want to look in the Developer Community. There appear to be some posts there about the symptom you describe:…

Hi @atta -- Welcome to the Atlassian Community! You may send the list of issues in the sprint, or even updates, using automation rules for Jira. Please look here for example rules and documentation information on automation: * https://www.atlassian.com/software/jira/automation-template-library#/label/all/1453 *…

Hi @Elena My understanding is that the roadmap colors match the epic colors. Have you tried changing the colors assigned to your epics? Best regards, Bill

Hi @Olive Sun What problem are you trying to solve by showing both the old and new keys in a filter result set? Thanks! Best regards, Bill

Hi @Anuradha Yadav In addition to the suggestions from @KAGITHALA BABU ANVESH regarding board filters... When you note the board for "PB Grooming" (refinement), what steps are involved in your refinement? * You may want to create and map any status values to columns for that board for refinement * And take note: if you…

Yes, I suspect that if you have two different fields with the same name within the scope of the project (or filter) that would cause problems for the gadget. I suggest working with your site admin to carefully ensure that you only have one field with that name in the scope. I note "carefully" as if you have multiple fields…

Hi @Gideon Nolte _Eficode_ Thanks for your walk-through on this approach. I definitely understand getting hooked on solving these automation puzzles. ;^) One need I find with complex rules is how to document the approach used so the rule is maintainable and not "too clever". I am trying to add an explanation paragraph in…

Hi @Áron I am glad to hear that helped. If you are interested in getting at the historical information using the REST API, please take a look at the explanation from @Gideon Nolte _Eficode_ in this thread. __Bill

Roger, if this helped you please consider marking this question as answered. That will help others with the same request find solutions faster. And, if you discover a marketplace add-on which meets your needs, please consider posting back here what you learn so others can benefit. Thanks!

Jon, I am glad that helped you. By the way, when hunting around for a smart value for a field you may use the method described in this article to help. It involves finding a representative issue/story and then calling the REST API for it; the resulting JSON will often show the smart value name.…

Hi @Roger Davidson That built-in bar chart is for a Sprint (as you note) and so cannot combine information for other data. The two closest matches (built-in gadgets) to get what you ask is the Pie Chart or the Issue Statistic gadgets. For more gadget options please check the marketplace for purchase options. Regarding…

Hi @Phlip Borgnes Another variation for automation is to leverage the Sprint field is a list, so when an issue finally moves to "done", the count of the number of sprints it took is: {{issue.sprint.size}} Best regards, Bill

Hi @Barbara Dewulf For your rule, please post an image of it and the community will be better able to provide suggestions. Here's an outline of what we did. If you want a more detailed explanation, I can add that, per your request. * First thing: chat with the team about measurement and interest level * Pause and consider…