My Company is developing in Scrum teams. Our requirements are based on processes which are decomposed into use cases and business rules. Is it possible in JIRA, to create new types of requirements, e.g. a use case?
The processes, use cass and busines rules, we actually manage in Confluence.
No, I mean JIRA issue types. It's a JIRA-specific phrase because that's how the functions are named in the UI and documentation. An Issue Type tells the user something about what the issue is being raised for, and for JIRA, it is a configuration hook - a lot of stuff can be made to hang off the issue type. For example, project 1 might have Bugs, Tasks and Stories in it (three issue types) and project 2 might have Requirements, Use Cases and Stories in it (three again). All six of those can have different workflows and fields etc. You can probably tell that in that case, project 1 is a simple development project and project 2 is more about design and requirement tracking.
JIRA supports as many, or as few, issue types as you need. A starting recommendation is to make them match your types of requirement.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs