How would I, Inherite the workflow of parent issue type to sub issue type.
ex- two diff sub issues under bug A (uses workflow grow oranges) and Issue B (uses workflow Grow Apple) respectively, should use parent workflow instead their own.
The sub issues you speak off essentially are just other issue types with your project.
The workflow scheme assigned to your project determine which workflows are related to which issue types.
If you wish certain issue types to use workflow A over B, you will have to change the configuration in the workflow scheme.
Be aware though, different workflow can use different statuses.
When you remap an issue type from workflow A to workflow B, all existing issues within the project will be moved to the new workflow.
If certain statuses in workflow A do not exist in workflow B, you will be required to remap these issues to an existing status in workflow B.
Mick, that's a static solution, what i was looking that JIRA should have some flexibility to use Parent workflow instead associated workflow to issue type.
I'm having 5 standard issue types and one sub issue type (named sub-task), so whenevr i am creating a subtask under any standard issue type- It shows the associated workflow but i would like to have an option (while associating a workflow to sub-issue type) to allow me to inherit parent workflow to Sub-issue type.
appriciate your help!
Many people use subtasks to assign pieces of the work to close/resolve an issue and the workflow isn't the same as the parent. You can create a new issue of the same type and link it back to the original. That gives you the same workflow and a logical connection between the two issues.
There is absolutely no way to do this in Jira without doing some significant hacking in the core code. The whole thing is structured on "issue type uses workflow". (By the way, I could ramble a lot about the idea, but Nick Massette and Joe Pitt have already said most of what I wanted to say)
It is an interesting idea though, and I'd be tempted to raise a feature request with Atlassian.
Before you do though, I think you need to justify the requirement, given that you're going to have users coming to you and saying "I created a sub-task and it's not letting me go to status X like the other one".
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot