Who's viewed specific issues in Jira?

[Henrik Mikkelsen]

In some projects I would like not only to know who's made changes to an issue but also who has viewed the issue and when.

Are there any audit-logs i can rely on?

Do anyone know a solution for this?

[Nic Brough -Adaptavist- · Accepted solution]

No, and it's complex to implement correctly.

One thing I've looked at in the past is the access logs - it's easy to scan those for <base url>/browse/xxx-nnn, and you could, in theory, do much the same by injecting tracking javascript into the issue view screen.

But that tends to miss a LOT of usage.  The manager who asked me to look at the logs turned out to be not viewing issues at all.  We knew he was seeing them, but he was using boards, dashboards, the issue navigator, IRC and email.  There's other routes too - REST and Confluence macros for example.

So, you're going to struggle to get any form of accurate data out.

[Henrik Mikkelsen]

Hey Nic, 

Thank you for a quick answer. Unfortunately not a very promissing one, though.

I think I can handle at least some of the problems with issue navigator and probably some of the others. I can make a company rule that only some fields are allowed in the navigator. And it seems I can check compliance in the database.

Emails are sort of solved. I tampered with the velocity files so it basically emails: somethings happened on your issue - and giving a link.

I've been thinking about the "Recent Issues" - anyone knows which table that is in the database? I might be able to dump the records from this?!

[Tetiana Khenkina _Enhancera_]

Henrik, it might be a bit late for you, but our recently released Access Log for Jira add-on is aimed at providing full access log functionality for Jira content and should satisfy your requirements. Please give it a try and let us know what you think.

[Adam Mason]

Has this been tested with Service Desk?  Does it successfully track customer view on the Service Desk?

[Tetiana Khenkina _Enhancera_]

Hi Adam,

We tested on Service Desk, but at the moment customer views are not being tracked.

We were planning to expand into customer tracking functionality. Is this a feature you are interested in? Please feel free to provide any extra details to support@enhancera.com.

[Alexey Matveev]

Hello,

If you are using Jira Cloud then you could have a look at a plugin called Who is looking for Jira Cloud 

https://marketplace.atlassian.com/plugins/whoslooking-connect/cloud/overview

I do not know if the plugin fulfils your requirements, but It is not that difficult to write such a plugin for Jira Cloud or Jira Server. You can find the idea behind the plugin here

https://bitbucket.org/atlassian/whoslooking-connect/overview?_ga=2.103876416.1509485013.1515994801-1659643416.1506407535

For the Server there is the same idea but different implementation

[Henrik Mikkelsen]

Hi Alexey,

Thanks. Real nice plugin :-). And I can see it's use

But if I understand it correctly - it will not help me directly in this problem? If I need eg an audit-log to determine that an user was looking at this issue on a specific date/time.

And I'm on server :-(

[IT Kobe]

Hello,

For Jira Cloud we have prepared app Friendly History for Jira . App allows you to get opened issue's views data such as:

• Total views count
• Last view date
• Time since last view (user other than current user)
• Last view by (user other than current user)
• Viewers count (who, how many views in issue, user's last view)

App also gathers more issue data in multiple various categories: Views, Assignee, Status, Worklogs, Comments, Links, Subtasks and Attachments.

Except raw numeric values here is example use case - you have users who were supposed to acquaint themselves with the ticket. This could be acquaintance with the requirements or a service ticket in the queue. In both cases, you are able to check whether the users did what they were supposed to and acquainted themselves with the ticket.

Here example of Views tab