Home Home
  login

Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Seeing different workflows for different issue types in same project?

web-app

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
MJD
Replies (1)
helpful
0
not helpful

Ah, nevermind.  Found the "Default Workflow" for setting up issue types, which is the source of the problem.  Someone set up "bug" to have a default workflow, and it overrides the project. 

Probably not the ideal setting in a shared environment, but that's a config issue on our side.


MJD
· 1
MJD