How to have sub-tasks inherit Fix Version field from their parent story.

Is there a way (without an add-on) to have all sub-tasks created to automatically inherit the Fix Version field value of the parent User Story?  We are starting to use JIRA in the government and add-ons just aren't going to happen right now.

 

The reason why I want this is because I have quick-filters for my backlog for viewing all of the different Releases that are going on.  If I click on the ABC 1.0 Fix Version, then it doesn't show any of its sub-tasks because the sub-tasks don't automatically inherit the Fix Version field from the parent story.

3 answers

Hi Chris, 

Are you using JIRA Cloud or JIRA Server? 
If you are using cloud then you can go to the workflow of the relevant project and add a Post Function on the Create Issue Transition. 
The post function you are looking to add is "Copy Value From Other Field". 
Configure the post-function to have Destination and Source field to pick Fix Version. 

And then choose to pick the version from Parent issue. 

If you are using Server, then there is no built-in feature like this. 
So you would have to either resort to add-ons or create an add-on for yourself. 

 

I'm not sure whether this is Server or Cloud.  In the "Add Post Function To Transition" page, there is no "Copy Value From Other Field" option.  There is, however, "Update Issue Field", but that only allows me to select from a small selection of issues (Assignee, Description, Environment, Priority, Resolution, Summary, Original Estimate, Remaining Estimate, Time Spent)

Does the URL for your JIRA instance starts with something like hostname.atlassian.net or is it your own hosted JIRA with your company name?
The above functionality works for JIRA cloud.

You must be using JIRA server. 
For that you'd need a plugin like "JIRA suite utilities", and with that you can use the copy value from other field post-function as I described above.

JIRA Cloud already has JIRA suite utility plugin pre-installed, so that's why the above function is already available there.

I don't think the program is going to spend $450 on this.  I simply want to have sub-tasks inherit the Fix Version field from the parent Story.  Is this little thing really going to cost money?

I've tried a couple of plug-ins, but they don't work.  Open to any suggestions.

Any updated information on this? From a UX standpoint this isn't really a "nice to have" it really should be default functionality that is offered; no way most companies will pay for this.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

Looking for anyone who made the switch to Data Center

The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...

34 views 0 2
Join discussion

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