Hello, I have JIRA cloud and a project setup called Art Outsource. These tasks are linked to a parent issue . When I set the task to in progress or any other status change I want it to update the Parent ticket as well but I cannot figure out the correct automation rules to get it working. I know there is an issue because the parent issues come from different projects
Here is what I have so far
This rule was configured with a project restriction. You can change this restriction in the 'Rule details' section. Only issues from the following projects or project types will be considered:AO
Can't branch rule as it requires issues to have been previously created by this rule. More than likely you have not yet created an issue or the issue(s) were created in an another 'If' block or branch - these would then not be visible outside of that block/branch.
Any help would be fantastic , thank you
I think its def a permission thing Im having our IT look at it, thanks guys for a direction at least
Yes but my problem is it will not do it for issues OUTSIDE my project due to some project admin rights but im not sure where to set those
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This rule needs to be managed from the Global automation rules interface:
If you click on All rules you should be able to see your rule, and then edit it, expanding the Scope to the additional projects you would like access to:
Note that if you are on the Free or Standard plan you will be limited to 100 or 500 multi-project/global rule executions per month:
(This info is buried in tables with awful pop-up windows here:
https://www.atlassian.com/software/jira/premium
https://www.atlassian.com/software/jira/features/automation)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Finally found informational pages, instead of big old ads. :-/
(Yeah, I liked the web better when the fanciest thing you could do was tables.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nice one @Darryl Lee
@Nick Barone if you can't evoke a global Automation rule, talk with your system admin, they will be able to empower it for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh man, good point @Curt Holley
Man, Atlassian really needs to build out their documentation for Cloud. I couldn't find documentation about Project administrators being limited to only creating Automations in their projects.
There's passing mention of it in these FAQs:
But that's an advertisement, not proper documentation!
Here's how Automation permissions are described for Jira Server (which is definitely different).
So it does like Cloud has this option as well:
(That's from my test Cloud instance.)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nick Barone
Welcome to the Atlassian community!
Wouldn't be as simple as this? (see below) and if you also want to update other fields you could add an "Edit issue" action and set that up to your liking.
Feel free to share more detail of the rules you have tried or the desired effect and we can assist you further.
Regards
Curt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.