Is there a way to copy a field to a linked issue on issue edit, using the plugin?

[Carlos Rincon]

Hi,

When I edit the fixVersion on an Epic, I want to automatically copy the fixVersion to some issues within the Epic.  Is there a way I can do this using the automation plugin (which I'm evaluating currently), or in some other way?  Some points to note:

• Using post functions I can do the job when transitioning the Epic but I want the copying to happen when I edit the epic, not just when I transition it.  So I guess if there is a way to fire a post function when an issue is modified, that would do the job.
• The issues I want to update are not in the same project as the Epic.  However I am ensuring that the versions to be copied exist in the target project.

Any help appreciated!

[Nick Menere]

Carlos, Casey,

Sorry but I forgot to update this issue.

Copying a field to a linked issue is trivial now. You should be able to do this with a rule like:

image2016-12-28 9:51:28.png

This rule listens for any change in the assignee and then copies that value to all the linked issues.

The secret sauce here is the "Related Issues Action" that allows you to iterate over issues related to the current issue - in this case linked fields. You can also select sub-tasks, parent, stories, epic and JQL.

Hope this helps.

Cheers,

Nick

[Carlos Rincon]

Hi Nick

It's been a while but I finally got to trying this.  The set-up is great and makes sense but it doesn't seem to be working for me.  I have:

"When: Value changes for Fix Version/s" ->

"Then: For Stories (or other issues in Epic)" ->

"Then: Edit issue fields".  The field I'm setting is Fix Version/s and I've set it to "Copy from Epic".

But when I edit Fix Version/s in the Epic, the issues in it are not updated.  If I look in the audit log, the rule ran with Status: Success, but under "Show more" I see:

BRANCH RULE / RELATED ISSUES
No related issues could be found.

Am I missing something?

Many thanks

Carlos

[Nick Menere]

Hey Carlos,

At the moment you can only act upon the issue that has triggered the rule.  We want to extend this to enable use-cases like yours. We would like to be able to perform actions on issues associated with the current issue - https://codebarrel.atlassian.net/browse/AUT-33

It being in another project could be another issue but we have some thoughts around that.

Until we implement that, you can use the transition to do this by creating a transition for the issue that loops back to itself. You can then use automation to to trigger the transition when the epic is updated.  It will stay in the same status but the post-function will be called.

Cheers,

Nick

[Carlos Rincon]

Thanks Nick.  Any idea if / when AUT-33 will be worked on?  Your suggested solution works but is also a little heavy in that I can't control which of the linked issues will be updated (which I will want to do), plus the original issue transition history quickly gets polluted with lots of transitions which are effectively NOPs.

[Nick Menere]

Hey Carlos,

We spent the last few weeks getting the Server version of Automation out. Now that is done we can get back to doing some more features. This one is near the top of our list so hopefully we will get to it soon.

Cheers,

Nick

[Deleted user]

Nick, I tried voting up on the ticket, but I can't see it any more now that I'm logged in. Let me say that I'm wanting the same thing(and should be a paying customer at this point).  Happy to beta test it as well!