I have problems with how Jira becomes an issue tracker, I don't think that its the best umbrella term for ( Epics, stories, tasks, sub-tasks, bugs, or defects,). How do I change that? What have others used? Maybe Work packages or Tickets sound closer to the umbrella term, issues seem more bud and defect, or is it just me?
Welcome to the Atlassian Community!
You can call issue types whatever you want, but I would not recommend moving away from the standards much, it's confusing for people who've used Jira before.
You can rename the Epic, if you have advanced roadmaps, but if you do, I wouldn't change it to anything other than "feature" to fit in with Scaled Agile frameworks.
There's nothing wrong with having an issue type of ticket, but it's a really bad word to use for the umbrella term - tickets imply someone has a right to demand a service from someone else, and bugs, stories, defects, assets and and and really don't fit that. It makes sense in a helpdesk situation, but in Jira, it's unhelpful because the users raise Requests (which can be of different types) and these are backed with issues, also of . If you say "ticket" to your admin, which part of it are you talking about? The request or the issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.