Keeping track of work items, and being tagged

[Kevin Gérard]

Hi Everyone! 

I'm comming to you with something i've been bothered with more and more often. 
Our organisation is growing ever bigger, and the context is more and more international. 

Jira has been giving us great tools & handles to keep track of our assigned tasks. Everything that includes following up of your day to day spaces works really well. 

Now we're encountered with some users that don't really have their own space, or fixed set of work items. These users have a lot of interaction throughout our entire site, mainly by being tagged in the comments, requesting specific actions or asking questions. 

These tags pile up, and are nigh infollowable. They get lost in the mailbox or notification systems... 

I'm wondering if there's a way in our Jira stack to keep track of your tags, and treat them like some kind of task list... 

How do you solve this challange in your company? 

[Trudy Claspill]

Hello @Kevin Gérard 

I don't think there is a native solution for making trackable items based on a user being mentioned in another item. There is not a "task list" feature in Jira like there is in Confluence. The items/issues created in Jira are the task list.

Your users could use the following JQL statement to find items where they have been mentioned in a comment:

comment ~ currentUser()

Being mentioned in a comment should add the user as a Watcher of the item. They can use this for finding items where they are a watcher:

watcher = currentUser()

They could refine the filter to exclude items that are already completed:

statusCategory != Done

A generic filter like this could be created, and a Dashboard could be created and shared with all users, where the Dashboard has gadgets based on that filter. Each user would see only the items where they are the watcher or mentioned in a comment.

[Bartek Szajkowski]

Hello @Kevin Gérard 

This is totally relatable problem 😊

If I may, I would like to propose you to check ARGON app (which you can find on Marketplace). You can turn those interactions into something much closer to a personal task list using advanced JQL functions.

https://marketplace.atlassian.com/apps/2170466783/argon-powerful-jql-search-for-jira

1) Track comment-driven requests
With the commented() function, you can surface issues where someone participated in the discussion. That’s perfect for building a personal “requests inbox” based on real interactions.
Example – find all issues where John Smith commented last year:

issue in commented("project = SER", "John Smith", "2023/01/01", "2023/12/31")

2) Track where you contributed artifacts
Many ad-hoc requests come with attachment (logs, screenshots, designs). ARGON lets you find issues where someone uploaded files, which often signals actionable follow-ups.
Example – find all issues where John Doe added attachments:

issue in attachment("project = TEST", "john.doe", "", "", "", "")

3) Prioritize where you might be blocking progress
Reactive roles often unblock others. With timeInStatus(), you can find issues stuck too long in certain states and treat them as implicit tasks.
Example – issues stuck more than 2 weeks in In Progress:

issue > timeInStatus("project = ABC", "In Progress", "2w")

Functions above are just a small part of what ARGON can do—there are many more advanced JQL functions and analytics capabilities that can help structure and surface otherwise hidden work.

I'm Bartek from Orbiscend OU, we provide ARGON app on Marketplace.

Hope my answer give you some another options in you future work.

Greetings

Bartek