Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Set epic name to an issue with JMWE

I have the following process in Jira Cloud:

Epic - Issue1(subtask1,subtask2,subtask3), Issue2(subtask1,subtask2,subtask3), Issue3(subtask1,subtask2,subtask3), Issue4(subtask1,subtask2,subtask3)

using JMWE I made the following:

when Epic is created an issue1 is created when issue1 is created subtask1 is created

this was made via workflows

What I need is:

1. When Issue 1 is created have the Epic Name field be populated with the Epic which it was created from to link them and use this link for issue2,3,4

2. when subtask3 is transitioned to done create issue2 which is linked to the epic


Thanks in advance if anyone can help

2 answers

1 accepted

0 votes
Answer accepted

Hi @Alex Koxaras thanks for your reply, this line really helped - What you want to do is to copy the Epic's key to the child's epic link field

I did the following:

1. Manipulate the issue workflow via subtask transition

2. Manipulate the epic workflow via issue transition

3. Set the epic link field value for issue1 to epic key

4. Set the epic link field value to copy from the current issue when the transition is making a new issue

Sound complicated but for me, this is a perfect solution.

Alex Koxaras Community Leader Nov 11, 2021


0 votes
Alex Koxaras Community Leader Nov 07, 2021

Hi @J M  

  1. First of all let me clarify that Epic Name exists only on epics. What you want to do is to copy the Epic's key to the child's epic link field
    epiclink rule.png
  2. For this request to work, I would suggest to create firstly a field (name it e.g. EpicLinkSubtask) which will hold the value of the epic key. Keep in mind that Epic - Subtask relationship does not exists. So you have to pass the Epic Link value of the Issue1 to the Subtasks(1,2,3).
    Then you would have to add a condition to that rule such as the following
    {% set subtasks = issue | parentIssue | subtasks("status") %}
    {% set trigger = true %}
    {% for v in subtasks %}
    {% if != "Done" %}
    {% set trigger = false %}
    {% endif %}
    {% endfor %}

    The above rule will be added to the done transition of your subtask
    create issue if all subtasks are on done status.png
Alex Koxaras Community Leader Nov 10, 2021

Did you manage to work it out?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

Send an Email or Publish to Confluence - What should you do with your release notes?

Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...

134 views 1 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you