The easy answer is "create a project and work with it".
For a more useful answer, you probably need to define roughly what you want from the project. Sketch up your desired processes and convert them into workflows. Work out what reports you want to be able to do, and use them to work out what fields and data you need in your project. Think through how your users want to enter and amend the data.
It doesn't seem like JIRA has transitioned to feeling like other than bug tracking. We don't like calling the tasks in our projects "issues". In IT when we hear "issue" we are on alert, it's very negative. I found where I can change the nomenclature of story, epic, initiative, theme, stream (though changing those changes them only in some locations but not all, which people found more confusing than before and we changed them back) - is there somewhere I can change "issue" to "task"?
Yes, it's true, it uses better language than most trackers, but it can be confusing. It consistently uses "issue" as a generic word to mean "something we need to do something about", and then implements a set of issue *types* to allow you to use whatever you like. If you don't like "issue" as a type, delete it. By default, there's already a "task" type in there.
Thank you. Do you know of a graphic that shows the hierarchy of issues, projects, stories, epics, initiatives, themes, streams? We're trying to figure out how JIRA Portfolio layers over JIRA. I think if we can get a picture of that in our heads it will help us map nomenclature to our processes.
Off the top of my head, not one that shows much of that. Plain Jira has a simple heirarchy - Projects contain issues, and issues contain subtasks. When you add Agile, then you get Epics added, which contain issues (Story is just a type of issue really) Themes are quite simple in Jira + Agile, they're effectively labels which you can brush across any Epics, stories or issues you feel like. Portfolio adds inititatives, which are similar to themes, in that you can pick and apply them across what you want, but there's a lot more functionality built into them than just "label some stuff that we should look at together" (themes) because you can plan and allocate resource against them. Streams are a way of looking at your portfolio from a release point of view (but I'm personally very hazy on that, as I've not used them yet)
Ok, on Cloud, I understand that you can't completely remove it. You should be able to disable it in the manage addons bit, but admins will continue to see the option in the menu to encourage you to use it, but none of the rest of the functions will appear to the users.
If you are looking for a MS Project flavor within JIRA, I really like BigPicture from software Planet. I recommend looking to see if this is more along the "traditional" approach you are looking for.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot