Hello everyone,
i have a automation rule that create a study on another project (with the same summary as the Epic) when label on an Epic contains a specific value.
But the study is created again if the label of the Epic change.
So i tried to check if a study with the same summary already exists.
but it seems that my condition No stories is not working as the create new is always triggered. Any idea ?
Hey Julien,
As you intend to use this automation between different projects in your Jira instance, have you checked to see if this is a global rule or a project rule?
The rule without the no stories was already working and was a global rule but you're true, it seems that if i add a condition, i should set it again to global.
I will see with admin as i don't have the right to do it on my own.
I'll let you know when it will be done.
Thanks for your answer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Certainly! I would love to assist further as I've had my fair share of automation :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Okan,
i tried the rule with a JIRA admin yesterday but didn't work either.
He puts the rule as a global rule but what i'm not sur is that on the new step there is always
which is the main projet
The admon told me it's not important but i'm not sure.
Any idea ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Julien, to the best of my automation knowledge, you have to have access to view and create issues in both projects if you're setting up a rule between the two. Also, the rule is restricted to OSS Delivery France but it needs to run in your instance to be able to locate the target project which is OSSFR_ARCHITECT. So, this rule restriction seems to be preventing the rule from running globally. However, Your Jira admin would be the best person to get support from in this case as they have full control over the instance and projects.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, it was a problem of rights on the condition.
Thanks for your support and help
all is working fine now !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My pleasure, Julien! I'm glad it's working now!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.