Specific Use Case Model: Changing Issue types while process

[Sven Müller]

I have a specific use case for jira, I have no idea how to aproach:

I want to track requirements from a customer. So he opens a new issue called "Requirement" and hands it into the process. An employee gets it and categorizes it.

There comes my question: I specified 4 types of issues ('Requirement', 'Bug', 'Improvement' and 'New Feature'). I want the customer to only be able to create a Requirement! Then my customers should categorize it into one of the other issues.

Could you please give me a hint how to model this use case into jira. Can I somehow define sub-tasks? How can I prevent creation of anything besides a 'Requirement'? Should I use conditions, so users cannot create bugs and other stuff? Am I forced to use the 'move' command to change issues?

Would be really thankful for help :-)

[Radu Dumitriu · Accepted solution]

You can have different customizations of your workflow. We did something very similar using our own plugin (https://plugins.atlassian.com/plugin/details/43318 - note: other plugins exists which can help ...).

So you definitevely need to write / use some plugins here.

1. Can I somehow define sub-tasks? - Yes, but depends on the problem you want to solve.

2. How can I prevent creation of anything besides a 'Requirement'? - Conditions on create, easy to do

3. Should I use conditions, so users cannot create bugs and other stuff? - Yes, see above

4. Am I forced to use the 'move' command to change issues? - Really depends on your solution. Usually, when you reach the 'move point', it means that the workflow is not doing what it should do.

[Colin Goudie]

This isn't supported in JIRA by default as far as I know.

Maybe you can approach it one of these ways

1. Create a custom screen or intranet page that allows customeres to submit issues but don't give them an option to select a type. You could even have this as the default issue creation screen in JIRA but I'm guessing your developers want to create any type of issue?

You could have a custom html page on your website etc.. that could do this and use the JIRA rest API to create the JIRA issue.

2. Create a plugin that uses a custom field and Javascript to check the user's group/permissions. (whatever is suitable for you setup). It could then hide the issue type combo box and just use the 'default'. users with the correct permissions would see the combobox and be able to submit anytype of issue.

This is probably more complex as there are multiple 'quick' ways to add issues in JIRA now so maybe a global piece of JS that runs everywhere in JIRA??

Anyway, some ideas to ponder