Bill Sheboy Expert

Hi @Michael Fuchs Are you using a Jira Cloud, standard license? If so, I believe the child issues of epics only show up as timelines on the roadmap for a scrum board. What are you using? Kind regards, Bill

Hi @maxime.demeestere -- Welcome to the Atlassian Community! JQL is not an SQL, and so it cannot do that. Your work-around options depend on how frequently you need this and your cost/effort limitations: * Need this one time* Export the issues to a spreadsheet and create the report there * If you need this a bit more…

Hi @Ofer Regev -- Welcome to the Atlassian Community! You are correct that those other levels are not supported by-name in the automation actions/branches...yet. Instead you could try to branch on JQL, for example: * trigger: issue field updated (for your field) * condition: issue type equals epic * branch: on JQL with key…

Rich, based on your rule and Curt's ideas, does your rule now look like this? Note I made a substitution in the JQL to check statusCategory instead of status. Please note: given the possible slowness of this rule, I still think it might cause a run-away, looping condition. Perhaps the 2-rule approach will cause the…

Hi @Rich Evers -- Welcome to the Atlassian Community! To confirm your use case, which do you mean: * when all of the sub-tasks of a story complete, do <X> * when all of the linked issues (of any type) of a story complete, do <X> * something else? Case #1 can be done in one automation rule, triggered on the sub-task…

Hi @Max Boerma Please try an advanced compare condition and test with the smart value {{issue.project}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ Kind regards, Bill

I believe this open defect is what you are seeing: https://codebarrel.atlassian.net/browse/AUT-1886 Unfortunately that one is in the Code Barrel backlog so we cannot watch it for progress.

That is curious...Two other things to try: In your rule, please try {{webhookResponses.last.body}} to see if that makes a difference when the response is a list; note the smart value is plural rather than singular. And try running your request from a browser to examine the response with your parameters to see if it is…

Thanks for explaining that, Jeremy. Is the specific user you want to update the person (user) who triggered the rule? If so, that can be found with the smart value {{initiator}}

Hi @Claus Lorentzen -- Welcome to the Atlassian Community! I believe that only an org admin can add/change another org admin. If you have at least site admin permissions, I recommend submitting a ticket to Atlassian Support to get assistance: https://support.atlassian.com/contact/#/ Kind regards, Bill

Hi @Jeremy Ens -- Welcome to the Atlassian Community! First thing: I do not have an answer to your question. Instead...I am curious what REST API method you used to access a property of an automation rule. My understanding is the REST API for manipulating rules doesn't exist yet. Thanks, and kind regards, Bill

Hi @Rodney Chan Yes, and...to what @Mikael Sandberg suggests: What type of projects are these epics in? Only company-managed projects use the field Epic Name, and so if some of your epics are in team-managed projects they would not be returned with that JQL. (Team-managed just use the summary field.) Kind regards, Bill

I agree that seems like a missing feature to me also...And FYI that I'm just another customer, and not an employee of Atlassian. :^)

Thanks @Kevin Bui What do you think of adding search results/tagging to the community automation articles on that documentation landing page, particularly where new features are introduced? (e.g. conditional list filtering, advanced branching, etc.) Those articles often demonstrate practical how-to use cases. Kind regards,…

Thanks for that information, Devanish. Essentially you want Jira automation to cascade change the start/due dates of the subtasks based upon a change to an "anchor" subtask, as would a tool like Microsoft Project. There are probably marketplace addons for Jira to make this much easier, and I recall that the roadmap team…

Hi @Frederik Vindum I believe this is still possible, and a bit risky. First I will describe a rule to try, and then some possible issues. * trigger: scheduled on JQL to find the issues with "CLONE -" in the summary: project = myProjectName AND summary ~ "CLONE /-" * action: edit issue fields to remove "CLONE -" from the…

Hi @Jim Stewart I believe you are correct that you need to calculate average velocity by hand, or... * export to a spreadsheet (or use the Google Sheets or Excel addin to make it repeatable) * investigate the marketplace for reporting/dashboard/ or JQL addons * build this with an automation rule (although it is a bit…

Hi @Pete Nathan -- Welcome to the Atlassian Community! Are you using a team-managed project? If so, configurable swim lanes are not available yet. Here is the suggestion to add that feature, as with company-managed projects. You may vote for/watch it to see progress. https://jira.atlassian.com/browse/JSWCLOUD-17580 Kind…

Hi @Anand Chilukuri -- Welcome to the Atlassian Community! Jira Cloud is a tool to support teams with their work, and IMHO does not fully support any specific way of managing work...which is a good thing: every team is different and what works for one team may not help another. If interested in a specific framework,…

Awesome! I am glad to learn that helped, Lynne.

Hi @Lynne Robinson If I understand your use case, you want to add the Next Unreleased Version to fixVersion in addition to any current values in fixVersion. Is that correct? If so... Short version: you cannot do that without a work-around Longer version: JQL knows about Next Unreleased Version for queries, and rules know…

Hi @eric.spink -- Welcome to the Atlassian Community! Please take a look at the description of that trigger in the rule editor: Rule executes when an issue is linked to another issue. {{issue}} will always refer to the source issue, so if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B. To access ISSUE-A,…

Hi @Vytautas St That is the correct smart value, and you may need to use dot notation to look for the specifics you need. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--webhookResponse-- Have you checked the status to confirm the request succeeded? Kind regards, Bill

Hi @Devanish Sahoo -- Welcome to the Atlassian Community! Would you please clarify your use case a bit? That may help the community to offer ideas. * You apparently have a story/task with more than 100 subtasks. Correct? * There is a "first" subtask which has a target start date. Correct? * You somehow have a way to…

Hi @Frederik Vindum First thing, would you please share an image of your rule? Did you somehow edit the link type, or remove/re-add the links with the type you want? Next, to process the existing issues you could: * copy your current rule * change the trigger to scheduled (e.g. once per hour) with JQL, looking for issues…

Hi @Guillaume Lebedel Remember that JQL is not a SQL, and so things like openSprints() probably only work with the actual sprint field, and not generically with any fields. You seem very close to a solution already, and if you do not need the actual "done sprint" value, how about this idea: just set a "hide" indicator. *…

Hi @Matt Pennock -- Welcome to the Atlassian Community! Adding to what Mikael notes: here is the suggestion to add Affects Version for team-managed projects. You may vote for/watch it to see progress. https://jira.atlassian.com/browse/JSWCLOUD-18747 Kind regards, Bill

Hi @Lennon Liao I have just confirmed for Jira Cloud that Project Admins, who do not have Confluence access, can indeed see this feature listed under project settings > features. My understanding from what you replied is that users without Confluence access will not see this feature option listed. That is a potential…

Hi @Brellison -- Welcome to the Atlassian Community! First thing: please consider creating a new question, and perhaps linking to related ones. That will ensure more people see it...only the people currently following this thread will see it otherwise. On to your questions... The rule you show is triggered on a field value…

Hi @Lennon Liao Thanks for this addition, and... * Can this feature be disabled for an entire Jira Cloud instance? * How does this feature relate to licensing: is it included in the Jira license or Confluence to use the feature? Some customers have different license limits for Jira and Confluence licensing, so opening this…