I come from a JIRA when it was just JIRA. Started at a new company and talk them into JIRA online for Defect Tracking for a software product and IT Support tracking. I instantiated our JIRA online as JIRA software and have questioned this from the get go. We are not a Agile development house. So I have to turn off anything agile to start with. Although that's not fun it's manageable. The problem that I'm asking about here is this. I no longer feel I really understand what Atlassian has done here as it relates to our needs. We need 2 type of projects:
Software Issue Tracking (standard JIRA old way)
Support Issue Tracking (as and IT department needs)
I can not see a Project type that really matches either. So I do a long process of converting an existing type (usually basic software) to these to needs. So that's my situation.
My question is: Is there a project type for standard Software and Standard Support type tracking defined anywhere that I'm just not seeing? In the old JIRA days I don't remember spend so much time configuring the projects.
If you wanted JIRA without Agile the choice would have been to go for JIRA Core. However, I believe that you have actually made a better decision although there is a learning curve to go through to get the most from JIRA Software. Let me justify such a rash statement.
Taking your requirement for Support Issue Tracking.
Now looking at your requirement for Software Issue Tracking
Now to pick up your point about the time to configure projects - I would suspect that in the previous company you had already established all your schemes and when you created a new project it was a relatively painless task to assign the appropriate schemes to the new project. Now that you are starting anew a lot of these schemes will require modification/creation and that is why it probably feels more challenging in time. The actual schemes are no different to what was there in earlier versions.
Sorry if this sounds a bit over the top as a justification for the decisions you have already taken but I would not worry about the word "Agile" as a concept rather focus on how you want to work.
I have been kind of doing what you said. But I change the workflow to match the old JIRA basic workflow. For IT Support and SW Issues: Open -> In Progress -> Resolved -> Closed For IT Tasks and SW Tasks: To Do -> In Progress -> In Review -> Done I think the Agile thing is just bothering me... I removed Sub-Task and Epic from the issue types. I'll look closer at the Kanban SW Dev project!
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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