Bill Sheboy Expert

I tried this for team-managed and company-managed. That JQL references a smart value, so you cannot validate it in the rule at design-time (which is why the button is grayed out): issuetype = Sub-task and parent = {{createdIssue.key}} We have extra issue types in our instance, so perhaps also check what the name of your…

Hi @Bridget Martin First let's confirm what I provided and you are using is working. So try writing that smart value directly to the audit log, perhaps with some text: Days difference: {{changelog.duedate.from.diff(changelog.duedate.to).days}} Next, I see a couple of things in your rule: a) At this time, created variables…

Thanks for clarifying, and I do not believe that is possible with the out of the box REST API. You could look at the change log for an issue, but you would need to grab each issue to check. You may want to check in the developer community to see if someone has solved this another…

Hi @Brock Jolet Have you tried changing the date into one of the other formats before storing it? You can then convert it back with toDate later. https://support.atlassian.com/jira-software-cloud/docs/smart-values-date-and-time-functions/#Smartvaluesdateandtimefunctions--- Kind regards, Bill

Hi @Andrew Lighten What do you mean by "get stories I worked on"? Do you mean issues you were assigned to at some point? If so... First try this filter to see if it returns what you expect, adjusting your project name and typing in your name to find your ID: project = myProject AND assignee WAS type-in-your-user-name ORDER…

Hi @Bud Herz As with similar needs not supported in out-of-the-box Jira, you can build something or buy something from the marketplace. (If you wait a moment a vendor, or three, will offer ideas... :^) To build this, you could add some custom fields, use automation rules to set them based upon status transitions, and add…

Hi @Jagz -- Welcome to the Atlassian Community! Please try to use the {{triggerIssue}} and drop the parent part to use the information from that issue. For example: iOS: {{triggerIssue.summary.substringAfter("Master:").trim()}} Note I added a trim() function to handle when the trigger issue optionally has a space after…

Hi @Guilherme Bombonato Vaz de Mello My understanding is: * The issues associated to an epic display in the issue view list as its child issues, and * The issues associated to an epic in the epic panel view are its child issues as limited by the board's filter. Please review your board's filter to see if those "closed"…

Hi! Yes, I saw that part. It also appears you are defining customProgress with itself. I bolded the part I wondered about: WITH customProgress=if(valueProgress): CONCAT("{color:green}", REPEAT("■", FLOOR(customProgress/10)), "{color}{color:gray}",REPEAT("■",10-FLOOR(customProgress/10)),"{color}") Thanks!

Awesome! I am glad to learn you solved it. For reference on some nuts-and-bolts details... Here is the article describing usage of created variables before/inside branches: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Create-variable-New-component/ba-p/1448118 At the time that article was written,…

Hi Darren, It appears you have a typo in your JQL for the branch. Here is an image of my test rule to do what you asked. Kind regards, Bill

Hi @[deleted] Yes, and...to what John notes, here is a suggestion to add collapse/expand components feature to the rules editor. You may watch/vote for it to see progress. https://jira.atlassian.com/browse/JIRAAUTOSERVER-262 Kind regards, Bill

Hi @[deleted] Yes, and...to what Alex notes, that linked post describes a work-around of using Send Email rather than a comment mention, and then use an email distribution group in the email's TO address. And, here are a couple of suggestions to support mention of groups, which you may watch/vote for to see progress: *…

Hi @David Dean Yes, and...to the suggestions from @Roberto Miasack What type of project are you using: team-managed or company-managed? For team-managed, issues drop off the board at 2 weeks, and there is no configuration for that yet. Here is the suggestion to add that…

Hi @David Dean Yes, and...to Jack's answer: I wondered about some things that may help you consider solution approaches. * What problem are you trying to solve by having this information? What would you do differently if you had that info now? * How large is your team? Is it so large that during any stand-ups, the team…

Hi @Jeffrey Cardona There may not be a "best" practice for this use case; how your teams work may help you decide what approach to try. Perhaps consider and discuss these ideas with the teams to help pick an approach, experiment, and inspect/adapt to improve. * Do people work on both teams, discovery and delivery…

Hi @Tania Mata Morales -- Welcome to the Atlassian Community! I believe that the basic roadmap built-into the free and standard license levels of Jira Cloud only displays -1 year to +2 years. Here is a suggestion to make that more configurable. You may watch/vote for the suggestion to see progress on it.…

Yikes! I am glad to learn you figured it out and resolved it. __Bill

Hi, Evan! After you create a variable, you may use it in the rule just like any other smart value. From your screen image, that would be {{lastUserComment}} I note where you are setting the value, you changed the syntax a bit. Didn't you want the actual comment? Something like: {{issue.comments.last.body}}

Hi, Community! Something I observed today for automation rules: {{createdIssue}} and {{createdIssues}} do not appear to return any sub-tasks created in a rule. (Verified through experimentation with Jira Cloud, company-managed and team-managed projects.) If you need to access those, you will need to use a branch later in…

Sorry; my bad...it appears to be a bit more complicated as I just discovered... {{createdIssue}} and {{createdIssues}} do not appear to return sub-tasks created in a rule! So here is the work-around for this which I tested and believe works as you asked: * trigger: issue transitions to Completed * condition: check if…

Darren, when you note it falls over on the JQL step, what do you observe happening and what do you see in the audit log? Thanks!

Hi @Alan Bowsher Agreeing with Jack and Alex on using automation rules... Another work-around is to create a saved filter, subscribe to it so you get emails of the details, and forward that to others (perhaps using an email applications rules). The key differences between this and the automation approach are: * With a…

Hi @Gurdeep singh -- Welcome to the Atlassian Community! Yes, you should be able to do this. Please review some of the examples in the template library and the documentation on branching to help you do this: * https://www.atlassian.com/software/jira/automation-template-library/most-popular *…

Hi @Cory Tsang Would you please clarify a bit what is happening and what you mean by "official Confluence link"? For example, what are team members pasting into the issue description and what happens when they do so? Kind regards, Bill

Hi @Alexander Agneessens To be honest, I am not using ALM Works. That being noted... Your definition of customProgress seems to be recursive, referencing itself. Did you instead want to use another value in the definition? Kind regards, Bill

Hi @darren.johnson I believe you do this with the same technique of branching on created issues, but alter your rule to guarantee the sub-task(s) are created first by changing the first branch. For example: * trigger: same as you note * condition: same as you note * action: create task issue, same as you note, and also…

Hi @[deleted] There is a recent open defect for this symptom, which you may mark as impacting you, and watch for progress: https://jira.atlassian.com/browse/JRACLOUD-77383 Kind regards, Bill

Douglas, I do not believe the built-in email handlers are very sophisticated in splitting/mapping data. This is why I suggested an automation rule also. Other alternatives are to build your own email handler or to investigate the ones available for purchase in the Atlassian marketplace:…

Hi @Chris Fortmueller I do this by adding a related issues condition to exclude them when checking a created issue trigger. For example: * related issues: linked issues * link types: "is cloned by", and "clones" * condition: are not present Kind regards, Bill