Hello, I have this issue which I'm sure should be very easy to solve, but for some reason doesn't work for me.
We use JPD, and have epics tied to the ideas. Epics appear under "Delivery work items". I'm trying to create an automation that does the following:
1. If an Idea Team field has changed
2. Update all the delivery work items (for us it's always epics) inside the idea.
I have an automation rule that seems to run but not take any action.
Anyone knows what might be the right automation for this?
Trying to attach my current automation rule:
Hey Rachel, welcome to the community!
I'm curious, does the log step provide any info?
One thing that might be useful is trying to get some log output from the branch work items to ensure you're in the right context for linked items. Does that make sense?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Jordan! Here is what I'm seeing. Since Jira automation didn't take any action, I'm thinking that maybe the problem is in the branching. I think that maybe "Types: added to idea" isn't representative of the actual relationship between ideas and Epics. BTW, here is also the test idea and epic I'm using. In the test, I'm updating the Team field in the idea, and looking to see if the epic is also updated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rachel, could you please check the scope of the branch? Does it include the other projects where the delivery work items reside?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ahh! That's one issue for sure. It was restricted to our JDP project. We also have a company managed project where the epics and the tasks are. Should I add the other projects in there?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Jordan, it seems I can't add more projects in the "Rule restricted to project" field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rachel, yes you will need to update the scope if you want the rule to be able to act in other projects. You can't do this from your project automation page but will need to go to the global automation administration page. Also, you can't edit the field directly on the branch but by updating the rule scope to include multiple projects, you will see that change reflected in the branch field.
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.
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.