Capture all Log of each ticket

[Amit.Kumar3]

Hi Guys,

I want to capture the specific log of each ticket like.

1) Ticket Number

2) All Assignee 

3) All Assigned To

3) Assigned Date

I want a report with above fields so that I can download and share the report further.

Note: there can be number of as

[Yuliia_Borivets__SaaSJet_]

Hi @Amit.Kumar3 

If you want to capture assignee changes, you can check the Issue History for Jira app developed by my team. Here, you can create a report showing the ticket number, all assignee changes, and the dates of changes.

Report example:

This report can be created to check the change logs of any issue field.

[Lisa Forstberg]

HI @Amit.Kumar3 ,

This is not a report or filter that you will be able to find out of the box in Jira.

Assignee can only be one at the time. Even though you can look in the history of every single ticket and trace who's been assigned at what time you can't pull this into filter, with a line per assignee and then export it. "An assignment" is not an object to query in Jira that has a start and an end date. 

Using WAS you can query Assignee WAS "user" to find tickets that a specific user has been assigned in.

In order to achieve the above you would need an automation that triggers on each assignment, saves these values into a custom field to be able to export that from a filter.

I am curious though, why is this needed and what will the data be used for? 

br

Lisa

[Amit.Kumar3]

Hi Lisa, 

Thanks for the response. But still I am struggling what will be the automation steps for this requirement. Can you assist if possible?

[Lisa Forstberg]

Still very curious about the WHY here...I highly suspect there are other reports that will create loads more value if you want to share the purpose of creating this report. 

By experience, all kinds of measurements of staff performance will eventually lead to a behaviour, and sometimes not the intended behaviour. Tracking time of assignment and either punishing or rewarding this might lead to users being reluctant to assign themselves, cherry picking what to assign or assign too much or sending the "hot potatoes" around the team assigning other members. Time and cognitive energy that can be better used.

That said if you still want to have this kind of report

If you need every single assignment action to be extracted for each ticket you will need to create a lot of text fields custom fields. One per expected assignment action (how many is likely? - can a ticket change assignee like 20 times in its lifecycle?)   "assignment #1", "assignment #2", "assignment #3" etc

Automation

Trigger: Issue assigned

Condition:  assignee not being empty

add branch: 

condition: "assignment #1" is not empty

Action: Edit field "assignment #1" set {{issue.assignee.displayName}} UTC {{now.shortTime}}

add branch:

condition: "assignment #2" is not empty

Action: Edit field "assignment #2" set {{issue.assignee.displayName}} UTC {{now.shortTime}}

etc..

---

This will print the full name of the assignee + the time of assignment in the text fields and you can create a filter in which every single field needs to be added as a column and then export that with "filter fields"

br

Lisa

[Marc - Devoteam]

Hi @Amit.Kumar3 

This is all specified in the history tab on each issue.

So this can be seen by anyone who is able to access the project, only browse permissions are required (customers excluded off course).

Just as @Lisa Forstberg is questioning, why is this information required to export outside of Jira?

[Amit.Kumar3]

Hi Marc,

Thanks for the response, But I am looking forward the automation so that I can see the results in a list view

[Marc - Devoteam]

Hi @Amit.Kumar3 

My question is why, just as @Lisa Forstberg

This information is already in the system, why need it outside the system.

If you intend to do this, you can check this article How-to-export-issue-history-from-Jira 

This article is written by an app vendor and provides options based on their app or you can use the API.

P.S there are more apps on the marketplace around history information.