There are a lot of issue types out there, and I'm looking for the best way to organize my project. It's 5-6 related enhancements to an internal app, done by a single developer, which will take a few weeks to complete. There will also be a QA and UAT person during that phase of the project.
For a single application with a handful of enhancements, I'd keep it simple. Create stories and tasks to drive the enhancements, let the developer break them up with sub-tasks if they want, and consider having "test" subtasks for tracking QA and UAT.
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