Creators of tasks and their roles

[Katarzyna Turnau]

Hi, I would like to understand what are the roles of JIRA tasks creators. For example I would like to have an answer to questions like:
1. Which role in the company creates the JIRA tasks the most, example answer: 50% of tasks creators are product manager/engineers.

2. Which role in the company creates the JIRA epics / tasks / stories / sub tasks the most?

3. Which role in the company adds / edits tasks descriptions?

Is there a way to check it?

[Evgenii]

Hi, @Katarzyna Turnau 

Welcome to Atlassian Community!

Your question is quite broad, so I’ll provide a general overview based on typical team members:

1. Who creates Jira issues?

• ~55% are created by Product Managers/Product Owners
• ~35% by Engineers/Developers or QA
• ~10% by Engineering Managers or Scrum Masters

Important note: In engineering-led companies (e.g., startups or platform teams), engineers/developers may create up to 70% of issues.

2. By issue type:

• Epics & Stories: Primarily created by Product Managers/Product Owners
• Tasks: Shared between Product Managers and Engineers
• Subtasks: Mostly created by Engineers/Developers
• Bugs: Typically created by QA
  
  

3. Who writes and edits issue descriptions?

Initial descriptions:

• Product Managers usually write the initial content for user stories and epics, including acceptance criteria.
• Engineers typically write or define descriptions for technical tasks, bugs, and subtasks.

Edits to descriptions:

• Engineers often update descriptions during development — adding technical context, PR links, or scope clarifications.
• Product Managers may revise descriptions to refine requirements or acceptance criteria.
• QA/Testers frequently add reproduction steps, environment details, or logs to bug descriptions.

[Trudy Claspill]

Hello @Katarzyna Turnau 

Welcome to the Atlassian community.

Are you looking for general statistics across the Atlassian ecosystem, or are you trying to pull statistics for your instance specifically?

If the latter have you done any configuration of your environment to provide information to Jira about the "company role" of each user?

Something I looked at recently is the app User Profiles. If you use Microsoft 365 as the backend for your user provisioning, this app can connect to that and pull additional attributes for each user, such as phone number, location, and company role, if you have that info as part of Microsoft 365. You can create custom fields for use in the work items that can be populated with data obtained through the app. Those custom fields can be used in JQL, so you can then start filtering work items based on the attribute associated with users in various User Picker fields like Reporter.

Disclaimer: I have never actually used the app. I discovered it while doing an Jira DC to Cloud Migration assessment for a client that uses the app in Jira DC.

[G subramanyam]

Hi @Katarzyna Turnau welcome to Atlassian community.

The details shared by @Evgenii might have already answered your query

Let's break down your questions, as I see an other side:

Jira stores key information for each issue. 

• Reporter: The user who originally created the issue (task, epic, story, sub-task). This directly answers your "who creates the most" questions.

• Updater: The user who last made any change to the issue.

• History Tab: Every change made to an issue, including description edits, field changes, and status transitions, is recorded here along with who made the change and when.

You queries:

1. Which role creates the JIRA tasks the most? Use JQL (issuetype = Task and look at Reporter), export data, and map Reporter to your "company role" list.

2. Which role creates the JIRA epics / tasks / stories / sub tasks the most? Same as #1, but use JQL like issuetype in (Epic, Story, Task, "Sub-task"), then group by Reporter and Issue Type.

3. Which role adds / edits tasks descriptions? This is harder to pinpoint specifically to description edits via standard reports. You can track who updated by the issue (description changed), but for precise "who edited what field," you might need to rely on exporting issue history or using a specialized BI tool that can parse the issue change log.