Why is JIRA issue activity is missing some activity items?

[Punit Jain]

An issue present in status A does not have any history for its movement to status A. Event the latest status item is regarding its movement from status B to status C.

Both the JIRA UI and API confirms the same

[Punit Jain · Accepted solution]

Hi All, This issue is resolved.
The thing was - someone changed the status name C(QA-AJEETESH) to A(QA-VARUN). That is why, I was not able to see any movement from QA-AJEETESH to QA-VARUN as they are same statuses.

Thanks for your replies

[Yuliia_Borivets_[SaaSJet]]

@Hi @Punit Jain 

Activity changes are listed in chronological order, not all statuses are in the same line. Have you looked below?

Also, you can check the Issue History for Jira app from my team. Here you will find history for the list of issues without the need to open and check each separate ticket. Maybe it helps if you see the general picture.

The add-on is available for a 30-day free trial, so you can check if it can help.

[Punit Jain]

Hi @Yuliia_Borivets_[SaaSJet] ,
Yes, I had checked all the fields. Out of the bunch present there, 4 were of the type status change, but none os these 4 had an history moving this issue to A(i.e. QA_VARUN)

[Nic Brough -Adaptavist-]

Check the history tab - that records all changes.  It might explain why the change to qa-varun is not part of the activity stream (if it was automated or triggered from the outside for example)

[Punit Jain]

Hi @Nic Brough -Adaptavist- ,
I had checked all the records of this particular issue.
Are automated events or events triggered from the outside not recorded as a part of the activity stream?

[Nic Brough -Adaptavist-]

Possibly - it depends on the event.

Did you find a line in the history that did not get echoed into the activity stream? 

[Punit Jain]

No, All lines of the history are present in the activity stream.

The history itself does not contain any line for the movement of issue to status A, so the activity stream also does not have any entry for it(or Vice-Versa).

[Nic Brough -Adaptavist-]

So the question is how did you change the issue into Status A?

I assume it was not created or imported in that status, so without a history line, we can't tell you what happened.

The only thing I can think of is that you have a script which is deliberately constructed to not write anything to the history.

[Fabio Racobaldo _Herzum_]

Hi @Punit Jain ,

welcome to the Atlassian community!

Is the status A first of your workflow? If so, JIRA track each change after creation.

Hope this helps,

Fabio

[Punit Jain]

Hi @Fabio Racobaldo _Herzum_ , No 
All the three - A, B, C are intermediate statuses