I am trying to implement a workflow for issuetype bug and another workflow for issuetype requirement. Requirement is a custom issue type. I have created separate workflow and workflow schemes for both the issue types. However, when I try to switch scheme, I have to map statuses for both issue types, which is messing up my workflows. Help?
Sounds like you are not quite getting how the schemes work.
I suspect the mistake you are making is that you've got your project set to use one scheme and you're moving the whole lot to another scheme. Rather than having a single scheme with two separate workflows in it.
Ok, so if i understand the steps above, this is what I need to do:
- Create a workflow for issue type bug
- Create a workflow for issue type requirements
- Create one workflow scheme and assign bug and requirement workflow with this scheme
- On the Switch Scheme page, associate the old status with the new status on the bug workflow and do the same for the requirement workflow
Please confirm...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes. That is right.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, so if i understand the steps above, this is what I need to do:
- Create a workflow for issue type bug
- Create a workflow for issue type requirements
- Create one workflow scheme and assign bug and requirement workflow with this scheme
- On the Switch Scheme page, associate the old status with the new status on the bug workflow and do the same for the requirement workflow
Please confirm...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are migrating both issueTypes to a new workflow then you would need to migrate both of them
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.