+1

Looking for a solution for this issue, I've tried the following JQL:

hissuekey in updatedBy("username", "2023-01-01","2023-05-01")

Is this what you're looking for?

Found in this link.

+1

Off topic, but JRASERVER is an odd name for a project. Reminds me of /usr in Unix. You couldn't have spared one more vowel??

+1

+1

+1

+1

+1

+1

+ 1

+1

+1

+1

I'm also looking for this. It would be ideal to be able to query "all the stuff I've worked on during the last few weeks" regardless of whether I've created it, updated the description, commented on it, added a label to it, etc.

Need it!

Added a vote for the feature and this is something I've searched for several times in the past.   Having a look back JQL query to show all activity would be a great help, especially in preparation for Daily Standup after a weekend where details of what happened last Friday are sketchy.  (They often are).   Or useful to search for Story that you modified or commented on, but now can't seem to find it.

This is also a feature I'm looking for.

Just querying who is Assigned to Jira is not helpful, if there are stale users or stale jira. Requiring people to log hours is not plausible. Checking that the Jira was updated in the last few days is not useful until it can check all the fields, including comments. It's also not useful because we only care if the Jira are updated by the development team, not the customers. If the customers are posting updates, then that's not an indication the the developers are busy doing work.

We really need a filter that says "show me all the Jira that have been updated by this group of users in this range of time.", and preferably the count of updates and the count of jira.

Hi @all, 

you may try "Power JQL: extended search functions", this should solve this and other search issues:  https://marketplace.atlassian.com/1216891

This Plugin give you Additional and useful JQL functions to search issues using the power of regex expressions! 

Best Regards
Domenico 

I'd second Steven's comment above - at least something like

comments changed by currentUser()

 would help a lot.

Some of the activity of most interest to me is when I helped colleagues in advancing their Jira issue.  In these cases I need to track comments I added to Jira issues created and assigned to others.  Not sure what work-around JQL I could use for that...

See header "Feedback Policy" in this ticket, points to:

https://community.atlassian.com/t5/Jira-articles/An-updated-workflow-for-Server-feature-suggestions/ba-p/721632#M113

How do we get this to Status "Review"?

Edit: Ah now I see, by votes and comments

Come on every voter, lets get this to status "Review" (now: "Gathering interest"). This feature is extremely helpful to track "what I've done".

Though https://community.atlassian.com/t5/Jira-questions/How-do-I-ask-JIRA-quot-what-bugs-have-I-modified-in-the-last-X/qaq-p/419367 has an accepted answer we would also like to have comments and progress included as well.

This is what I currently use:

status changed by currentuser() after -30d  OR created >= -30d AND creator = currentuser() OR assignee changed by currentuser() after -30d  ORDER BY updated

Basically, it is visible if you have a look on you open your profile. Maybe this helps in solving the issue or can be used as workaround.  

@Andree Knoche: Have no idea about who you are but your comment just made my day my friend.

Had a change to visit Viet Nam, let me know then I will show u everything 

This Issue has celebrated its 10th anniversary and I would like (in good Atlassian manners) to remind it again. 

This would be extremely useful. For anyone who is managing/routing tickets vs. burning them down directly, or anyone who collaborates on a ticket they did not apply hours to for some reason or other this is very useful. This feature would make JIRA more useful to the softskill side of a software team, and encourage collaboration from a wider audience. As a former TFS user coming to JIRA, I think the search/query/notification functionality in JIRA tool lacks the deftness and efficiency of TFS. (I don't claim TFS to be better overall, but the ability to query and alert work items IS better in TFS).

Yes, I agree, this would still be useful

For those who are interested: As workaround for this, I use the Activity Stream Gadget in a private Dashboard.
Its not exactly the same, but you can at least get the nessessary information by filtering by user and update date (however every filter change needs to be saved every time, so the dashboard is private).

Any plans to implement this before it hits its 10 year anniversary as a request? 

Greetings,

I was directed to this ticket via a ticket I opened concerning issues getting accurate historical numbers for our unassigned ticket queue via the Service Desk reports.  Our unassigned queue workflow is as follows:

workflow:

1. Ticket is created.
   • When created, the ticket is Unassigned and in the "Queued to Core Speech" status.
2. When a member of the team is ready to take on another ticket, they assign a ticket from the Unassigned Queue to themselves and move it over to WIP.

The issue we're having with the reports is that, once a ticket is assigned, JIRA seems to lose track that it was ever in the unassigned queue during whatever time it spent there. Put another way, it's like the ticket was never in the unassigned queue. Here are some different ways we've tried to report on this via the SD reports:

status = "Queued to Core Speech" and assignee = unassigned
I also tried:
status was "Queued to Core Speech" and assignee was unassigned

The reason I'm posting here (since this ticket isn't really about SD features as much as JIRA in general) is because I sort of found a workaround to this.  It won't make the SD reports capable of historical reporting; however, it will give us the ability to see our historical unassigned queue numbers until SD is capable of reporting on it.  Here's what I did to get this to work:

1. Created the following filter:
   1. status was "Queued to Core Speech" AND assignee was unassigned
2. Use this filter for a Created vs. Resolved gadget.
3. Use the following settings for the gadget:
   1. Period - Doesn't really matter.  I went with weekly for now.
   2. Days Previously - Doesn't really matter.  I'm using 300.
   3. Cumulative Totals - Also doesn't really matter.  I selected "Yes".
   4. Display the Trend of Unresolved - YES.
   5. Display Versions - Doesn't matter.  I show all versions.

The Created vs. Resolved part of the chart isn't what's important here.  Take a look at that trend line.  That almost exactly matches the historical unassigned queue numbers we were expecting to see.  Not sure if this will be applicable to anyone else here, but figured I'd post this just in case.  I'll also attach a screenshot of the final product.

Yeah, another example is I have a Quick Filter on my Agile board for updatedDate >= -2h but it often includes the issues that I recently updated.

I would like to filter these out so I only see the updates of others, not myself.
It's worth noting that the issues are all created by me but not assigned to me so I can't filter by assignee.

Is this the right issue for that?

The HP/Palm Jira Search Plugin has an option that will search the entire issue change history, including who changed the field and when it was changed. When this feature is installed, then you can use the issuesTouched() JQL function in the plugin to search exactly as this issue suggests

This improvement is closely related to JRA-12094 and makes up a part of a larger feature request - JRA-5536 - to be able to search through issue change history.

Please note that at the moment there are no plans for implementing this functionality.

For more information on the way new feature and improvement requests are scheduled, please see:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

Cheers,
Anton