Is there a way, that an issue is somehow marked/flagged if a new assignee has opened the issue? I mean, if I assign an issue to a user, I'd like to know if he/she opened it at least once - this gives me knowledge, that the user is aware of the issue and I have no need to poke he/she regarding this.
Once added if the assignee accesses the issue, a worklog entry will appear in the issue stating 'I accessed the issue'
There is no such thing as a read-receipt (if that's what you're looking for).
The only solution I see is that you set up your notification scheme to alert the new assignee of the new issue and that should alert him/her to start looking into it. Since the alert mail itself already contains lots of information about the issue you could consider this as your "poke".
hope this helps,
Jira doesn't log reads - it would be an absolutely massive overhead, inefficent and painful to implement for very little benefit. I doubt it'll ever be implemented, and it would probably be quite difficult to do by hacking the code.
If you've got Apache or a web-server in front of it, you could try to do something horrid like parse the incoming logs for "browse to issue X", but to give you an idea of how much fun that would be, we generate 2Gb of Apache log a day.
The whole point of the email system is to give your users the "poke" you're asking for. If they choose to ignore it, change your human processes to say "do not ignore Jira emails".
I can't completely agree. What overheads are you speaking about? When a user opens an issue, he/she creates an 'overhead' for DB and connection anyhow, which has much bigger footprint than a single flag. For example, this site with QA does log views and did not choked by 'overheads'.
I'm asking not about poking itself, but about back notification if the poke succeeds. Jira is a tool for changing human processes. If we could change the human processes just so simple, then Jira would be useless.
I think nowadays there is a lot of (may be most of) web-applications which track user activity on the fly and show it.
I didn't say that they ignore something. But there exist many different circumstances under which users may react to new issues with different latency, and I'd like to know if this happens.
Hello Community, Today we are going to talk about the three Scrum Roles. There is the Development Team, the Scrum Master and the Product Owner. In my opinion these three are all really impo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs