When starting out with JIRA is it better to use the JIRA Default Schemes? OR should I be customizing projects? The ultimate goal is to use this for development cycles, bug tracking and project management (across departments).
Any tips, insights, articles to read would be great!
IMHO, you should leave the JIRA Default Schemes alone. If you need a new scheme, make a copy of it and rename it as you see fit. There is no way to revert it back to the original unless you manually edit it.
Or unless you want every other project created to use the "edited defaults", then go ahead.
I don't think I ever used the default schemes. I started experimenting with custom workflows from day 1.
Here's a typical workflow we use for bugs:
For Subtasks and other task-like issues:
Of course, these are rather simple, and we have loads of variations depending on the type of project, issue type and teams. Some teams like to have validators in transitions to force people to comment when setting an issue On Hold or to ensure that all sub-tasks are done before you set the parent issue to Done. Some teams want transition screens everywhere, while others don't want any. Developments projects use workflows more adapted to Scrum, while support projects are closer to Kanban.
I strongly suggest you get acquainted with the advanced workflow configurations, and be on the lookout for plugins that make your lives easier (JIRA Agile, Structure, Scriptrunner, Issue Templates, Quick Subtasks, JEditor, JEMH...). I could go on.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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