Bill Sheboy Expert

Hi @Jon At this time for automation rules, I believe you can only add links to the attachments in the linked story comment. Selecting such a link will download it as a copy, and will not open within Jira. If that would work for you, this will produce a list of links to the attachments for the triggering issue: Here is the…

Hi @Roger Davidson Would you please describe what it is you want to see (the problem you are solving)? That may better help the community to give you suggestions. Thanks! Best regards, Bill

Hi @Nancy Latimer If you have one of the versions of Automation for Jira, you may to do this with automation rules. There is a free version (lite) for Server also. For example, this would list the voters as a comma-separated list for an issue: * Voters: {{#issue.voters}}{{displayName}}{{^last}}, {{/}}{{/}} And the vote…

Hi @Tara Woodham What add-on product are you using to create that report, as I do not believe there are built-in Jira Cloud functions to generate such information? Knowing that information may help the community better answer your question. Thanks! Best regards, Bill

Hi @Raffaele Litto Have you tried {{issue.sprint}} yet? That is a list of the sprints an issue has been assigned to and which have at least started. Here is the documentation on the value to see what is available within it:…

Hi @Samantha Johnston Have you considered using quick filters for your release information? You may then enable/disable them as needed on the board or backlog views. We found the following two quick filters helpful... Next release: fixVersion = earliestUnreleasedVersion() All later releases: fixVersion !=…

Hi @Deepanshu Natani There are lots of marketplace add-on products to do this measurement. If you do not want to purchase them, you could add a custom field (or a few for different status values or categories) and use a couple of Automation for Jira rules to maintain the value(s): * One rule to start the clock on a…

Hi @Áron As you note, for future transitions this problem is straightforward to solve: save {{now}} on the transition. For prior items which are still in progress, you can use this to capture the start of the first "in progress" category status: {{issue.statuscategorychangedate.toDate}} For prior items which are are now…

Hi @daljitsb -- Welcome to the Atlassian Community! If you search the marketplace for JQL add-ons, you will find tools that could help with your request: https://marketplace.atlassian.com/search?hosting=cloud&query=JQL Depending upon the number of issues you expect back (and the number of epics), you could also use an…

Hi @Flavia Oliveira I was suggesting that after the Trigger, you could add a Log Action to record the value of {{issue.epic link}} to the audit log. Then when the rule runs you may check if the triggered issue has the epic you expect. Please look here for information on the Log action:…

Hi @Mark Haller I believe that you can do this with RegEx comparisons. Also, you may also want to account for the time zones, such as from the reporter. Here are the details, if my image is not clear, using If/Else, with an Advanced Compare Condition with two clauses. For the day of week use: * First…

Hi @SUNMI HELP DESK Please review this documentation to see examples of using the string parsing functions for automation rules. After you see what is available, you can try to use those to search the email address suffix. https://support.atlassian.com/jira-software-cloud/docs/smart-values-text-fields/ Once you start…

I do not understand what you are trying to achieve when you note "target mailbox". Have you investigated using the string functions like match() with RegEx expressions for the searching?

Hi @Zaid Darras I believe there are marketplace add-ons for purchase which support version managment like that. But nothing in the out-of-the-box Jira Cloud Standard version. You could build something using automation rules (global/multi-project) such that when a Version is created is is also created in other projects.…

Hi @syee -- Welcome to the Atlassian Community! You have two questions, with some overlap between them. 1) Is there a possibility to extract data from a burndown chart? No, but you can pull the Sprint Report as JSON for a completed sprint using the REST API, substituting in yourCompanyInstanceURL, yourBoardNumber, and…

Hi @dyonata_ramos -- Welcome to the Atlassian Community! Would you please describe the problem you are trying to solve with your request? And, what does your team's definition of done say is included in the work to "done"? For the steps you describe, VALIDATION is part of how you work today, and so it needs to complete…

Hi @Cow Hills Now that we know you are using Jira Server, I would like to suggest a pause and ask you to post an image of your entire automation rule. That may provide more context for the community to offer ideas. Thanks!

Hi @Rebekah Wood -- Welcome to the Atlassian Community! What problem are you trying to solve, or what questions you are trying to answer? Knowing that will inform the options available to create reporting, and help the community give you ideas. For example, * you may be able to do what you ask with existing built-in…

Hi @Lacey You may want to review the backlog item for the New Issue View and the sub-tasks related to comments. There are several related to what you are asking about. https://jira.atlassian.com/browse/JRACLOUD-70555 Best regards, Bill

Hi @E You are checking for things added to the sprint AND removed from it. If you change your AND to an OR it should work as you expect. Best regards, Bill

Hi @Albert Manuel Have you tried putting quotation marks around the smart value? The field type and value may be leading to the invalid JSON error you note. { "fields": { "customfield_10951": "{{issue.customfield_10951.value}}" } } Best regards, Bill

Hi @Slava Shpitalny I do not believe you can trigger an automation rule on PR title change. These are the PR-related triggers currently available: * Pull request created * Pull request declined * Pull request merged Best regards, Bill

Hi @Cheong sanghun You note that you are using a time tracking plugin. I suggest you start by checking the documentation for that product to see if there is a built-in feature to zero out the time. If that is not possible, next check if the fields for the time tracking app are accessible to Jira for Automation rules. And…

Hi @Hunter1428 Would you please provide an example of your automation rule's email content that is not keeping the formatting? Thanks! Best regards, Bill

Hi @Shital Khaladkar Please try this to get to the list of issues in the version, replacing myCompanyInstance and myProject: myCompanyInstance/browse/myProject/fixforversion/{{version.id}} Best regards, Bill

Thanks for that information, Kitty. Rather than going too far back in sprint history, you may want to consider monitoring this sprint-by-sprint to evaluate improvement. And, perhaps look at team-based sizing methods to help add routine habits to build estimation skills: * Definition of done for sizing * Sizing ruler: using…

Hi @SUNMI HELP DESK Please try putting quotation marks around the smart value tag, such as with: { "fields": { "customfield_10146": "{{issue.reporter.emailAddress}}" } } There may be something in the email address that the parser doesn't like, and so the quotation marks should help. Best regards, Bill

Hi @Patricio Rodriguez Thanks for that information. Just to confirm, are you showing the pie chart for the entire project or for a specific filter? In either case, "irrelevant" seems to appear in two cases: * When issue values are transitioning from one value to another. If you are consistently seeing this value, that is…

Hi @Cow Hills This is inside of the iterator processing for {{#issue.attachment}} so have you tried just {{id}} by itself? Best regards, Bill

Hi @Wes Thoemke -- Welcome to the Atlassian Community! You note that your company is using a plug-in to Jira; what plug-in is that and who is the vendor? Knowing that will help the community provide you with suggestions. Thanks! Best regards, Bill