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?
Seems liek a feature request: https://jira.atlassian.com/browse/JRA-5225
As described by other users in the feature request, there are some workarounds, such as the Minyaa Suite plugin: https://marketplace.atlassian.com/plugins/jira.plugin.minyaa
Or the JSS plugin: https://plugins.atlassian.com/plugin/details/16346
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): issue.setComponents(issue.getParentObject().getComponents()) issue.setFixVersions(issue.getParentObject().getFixVersions()) issue.setAffectedVersions(issue.getParentObject().getAffectedVersions()) issue.setPriority(issue.getParentObject().getPriority())
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...
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!
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