Seeing different workflows for different issue types in same project?
Hi,
Having an issue I can't understand. We recently migrated from a system where different teams each had their own Gemini instance to a shared Gemini instance.
My team uses a different vocabulary and different workflow than other teams. I figured things would be OK if I set up a custom "Issue Type Scheme" and "Issue Workflow" and assigned them to our project.
This MOSTLY worked--the 2 "Issue Types" that are custom to our Issue Type scheme properly show the Issue Workflow statuses I expect. However, there's one issue type ("Bug") that we share with other teams (it's in both our Type Scheme and their Type Scheme). That issue type was a problem--when I try to create an issue and set to type "Bug," I see the default workflow, not the assigned project workflow.
This is very strange to me--as I understand it, "Issue Workflow" is a project concept. I expect all issue types in the same project to use the same workflow. But that's not what I'm seeing--one issue type has a different workflow, and I can't seem to resolve that issue (there's no way I can see of attaching a workflow to an "issue type").
I was able to resolve the issue by creating a new Issue Type called "Defect" and using that instead of the shared Issue Type "Bug". This fixed my problem, which leads me to speculate that the problem was indeed that we were sharing an Issue Type between projects with different Workflows.
Is this a known issue? Is there a better way I could have resolved this without hacking in an artificial difference between "bug" and "defect"?
MJD
· 1 |
|
Thursday, November 18, 2010, 7:11:34 PM |