What people call Issues

[Sonja Altmann]

Hi there,
Just curious, maybe I'm wrong, and am interested to hear other's thoughts.

People in my organisation refer to everything that lands in a Jira project (ie Epics, Stories, Tasks, Sub-Tasks etc) as "Jiras".

I work in the area of documenting the business processes, training people and providing information so I will get to hopefully influence this vocabulary.  

But what if I'm wrong? 

I call them Issues.  

Should I be calling them "Jira's".

I probably shouldn't care.  But somehow I do!  

Hit me with your thoughts!

[Pasam Venkateshwarrao]

Hi @Sonja Altmann 

The Epic,stories,Tasks,subtasks all these are issuetypes which user can create a jira ticket by using issuetypes based on their activity.

[ariraati]

I prefer to call them as issues too (never heard someone calling them as Jiras, for me that sounds like nickname). And when specifically referring to a specific issue use its issue type name (Epic, Story, Task, Incident..) to give reader idea what the issue is about.

[Linh Pham_Ricksoft_Inc]

In my organization, all issue types in software projects are called "tickets" but those in business project (JWM) are called "tasks" but in general we also refer to them as "issues" :D 

[Nic Brough -Adaptavist-]

They're all issues, as Jira is an issue tracker system.  "Issue" is a generic term for "something that needs to be looked at"

Some people use the word ticket, which is generally wrong, because in English, a ticket is only one possible use of an issue item - Epics, onboarding processes, post-it notes on your 'fridge, etc - are not tickets, but they are issues.  A ticket is something that gives you an entitlement to a service provided by someone else.  I'd accept the use of the word "ticket" for a Jira service-management Request and Issue pair, but not most other issue types (unless you really are using Jira for running trains or bus services)

But some places do call Jira issues Jiras, and there's nothing wrong with that, it's a perfectly valid way to talk about issues held in Jira.  It's likely that it is localised jargon, just the way your organisation happens to talk - I've worked in a couple of places that called them Jiras, and many that do not.

The only thing I would say about the way you refer to issues in general is to NOT have an issue type with the name you choose to refer to refer to all types of issue in Jira.

[Brent Lightsey]

I personally despise that  they chose "issue" to really mean "item" because Jira has evolved into a Project Management system, not just an issue tracking system. In Project Management, an issue is defined as:

"Issue. A point or matter in question or in dispute, or a point or matter that is not settled and is under discussion or over which there are opposing views or disagreements."

source: https://projectmanagement.com 

I have always thought of an issue as a problem that needs to be solved or an unknown that needs to be answered. It's just not an accurate generic term for some kind of record that take on various types. I hope one day we can change the terminology, but I'm not very optimistic. I think the word is just too ingrained.

When we talk to non-Jira users about our backlogs, it just throws a negative connotation if we constantly use the word "issue", but we become inured to it internally through constant usage.