History visible for reporters

[Alejandra González]

Hi,

I would like to know if there's an option for reporters to see the history of the tickets and all the assignees that have worked on it. The only option right now is through mail but its not efficient neither scalable . The other option is through the customer portal but it just shows the current assignee or the final one once the ticket is closed.

Thank you

Alejandra

[Yuliia_Borivets__SaaSJet_]

Hi @Alejandra González 

1. You can open the history option for each ticket. You'll find it in the Activity section. There is available info about assignee changes.

2. If you need a more extensive view (for list of tickets), you can check Issue History for Jira.

My team has developed this plugin as a journal for every past activity. You can filter tickets by reporter, assignee, project, date range etc. Also, you can select add or rearrange the columns.

Let me know if it helps or if you have any questions.

[b_hassan21]

Hi @Yuliia_Borivets__SaaSJet_ 

With your plug in can I pull the historical data of the sprint once it's closed.

Eg: I like to pull data of last 5 sprints, that how many issues were created and completed?

[Yuliia_Borivets__SaaSJet_]

Hi @b_hassan21 

Yes, you can see data for closed sprints. Every issue update will be fixed. For example: who has moved the issue from in progress to done.

You can filter by sprints or date range and add any columns you need as created or resolved. Also, export is available, so you can analyze data further.

[Tansu Akdeniz]

Hi @Alejandra González 

You could simply define a new automation rule from project -> project settings -> automation. And when the assignee is changed, you can add assignee info via public comment. So, every assignee change can be tracked within the request in portal.

Also please vote this issue JSDCLOUD-2044.

[Alejandra González]

Hi @Tansu Akdeniz 

what's the exact action to "add assignee info via public comment"?

Is this first trigger correct?

[Tansu Akdeniz]

Yes. But you don't need to select "Transition Issue". If you select, assignee changes without changing statuses won't be listened.

Sample:

[Alejandra González]

@Tansu Akdeniz Great thank you!

One last thing, can it be even more specific as it is internally? attach an example of a more in detail way

the current way is less intuitive:

[Alex Tucker]

How can a public user who is a reporter without a Jira account see the ticket history?

[Yuliia_Borivets__SaaSJet_]

Hi @Alex Tucker 

You can export ticket history if you need to present it to external users:

How to export issue history from Jira?