In GreenHopper 6, can I create subtasks that inherit field values from the parent task?

In the Classic Boards, if I create a subtask within GreenHopper (using the "cog" menu, Add Sub-task), some of the fields (Assignee, Component, etc) are prepopulated with the partents values. This is usually desirable and can save a lot of time.

However, in the GreenHopper 6 boards, the equivalent action does not provide these prepopulated fields. There are some, like reporter, that default to the user doing the action, but not Assignee, Component, etc.

Is there a way in GreenHopper 6 to get this old behavior back?



1 answer

1 accepted

1 vote
Accepted answer

Seems liek a feature request:

As described by other users in the feature request, there are some workarounds, such as the Minyaa Suite plugin:

Or the JSS plugin:

Within the project Workflow, navigate to the the "Create Issue" transition (first transition in a workflow under Open), then add a JSS Post Function script to copy whatever fields you require

if (issue.getParentId() > 0):

Thanks Daniel,

I'd searched around using various keywords and wasn't able to find this myself, but this is useful. I voted up JRA-5225 and am watching it, and I will investigate your suggested workarounds.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,086 views 4 9
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you