Specific Use Case Model: Changing Issue types while process

Sven Müller3

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

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.