• 9
    • 3
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Atlassian Update - 23 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      At this time, this suggestion is not on the JIRA development roadmap; however, there are a number of third-party plugins mentioned in this post from Atlassian Answers that can accomplish this.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      I am looking for a way to search for all tasks that a specific user has been involved with.

      For example:
      Tom creates a jira task and assigns it to Sally.
      Sally logs work against the task and runs into a road block that only Jim can solve.
      Sally assigns the task to Jim.
      Jim logs work on the task and assigns it back to Sally.
      Sally logs work and resolves the task.
      Tom reviews and closes the task.

      The task now shows Tom as the reporter and the Assignee. There is no way to know that Sally and Jim worked on the task.

      It would be nice to have a search option to find out that Sally (or Jim) contributed to the task.

      This relates somewhat to JRA-6137

        1. assignee changed.jpg
          assignee changed.jpg
          20 kB
        2. assignee changed.jpg
          assignee changed.jpg
          20 kB

            [JRASERVER-12312] Search by work log user entries

            +1

            Furkan Akduman added a comment - +1

            Definitely need this

            JQL looks second rate without having query access to all worklog fields

             

            Fix this and my queries wont load the DB up so much. currently have to query everything

            Tim Ballingall added a comment - Definitely need this JQL looks second rate without having query access to all worklog fields   Fix this and my queries wont load the DB up so much. currently have to query everything

            +1

            Tyler Anderson added a comment - +1

            This would be very useful for us too, however we do not use Jira server anymore. Is there a new separate request for the same functionality in Jira data center somewhere else?

            license management added a comment - This would be very useful for us too, however we do not use Jira server anymore. Is there a new separate request for the same functionality in Jira data center somewhere else?

            +1

            Adam Hemeon added a comment - +1

            +1

            Julia T added a comment -

            +1

            Julia T added a comment - +1

            Jim.Sears added a comment - - edited

            Free!

            Jira Assistant is a free robust extension I use with Chrome that has worklog features. The report can be filtered, sorted and grouped by project, issue type.

            I don't know if everyone's specific use case is covered but I find it useful.

            https://chrome.google.com/webstore/detail/jira-assistant-worklog-sp/momjbjbjpbcbnepbgkkiaofkgimihbii

             

            Jim.Sears added a comment - - edited Free! Jira Assistant is a free robust extension I use with Chrome that has worklog features. The report can be filtered, sorted and grouped by project, issue type. I don't know if everyone's specific use case is covered but I find it useful. https://chrome.google.com/webstore/detail/jira-assistant-worklog-sp/momjbjbjpbcbnepbgkkiaofkgimihbii  

            This would be incredibly helpful for us.  I need to find a way to report out on how many tickets are answered by each team member as well as turnaround time and cannot currently find a way to do this without having to open every ticket.

            Kathy Ellis added a comment - This would be incredibly helpful for us.  I need to find a way to report out on how many tickets are answered by each team member as well as turnaround time and cannot currently find a way to do this without having to open every ticket.

            We do lots of pair programming and this would be very useful to facilitate time tracking for the two users who are doing the pair programming. Right now we are opening two tickets for the same work so they can each be assigned to an engineer. This would help us avoid having to open and track two different tickets.

            Keaton Babb added a comment - We do lots of pair programming and this would be very useful to facilitate time tracking for the two users who are doing the pair programming. Right now we are opening two tickets for the same work so they can each be assigned to an engineer. This would help us avoid having to open and track two different tickets.

            This would be a great feature!!!

            Tracy.Martin added a comment - This would be a great feature!!!

            Joerg added a comment -

            If you do this, then the results need to respect Worklog visibility!

            Jqls already do not respect it (which is BAD), but luckily only return the total time spent, and not the time per user, which would be a GDPR problem.

            Joerg added a comment - If you do this, then the results need to respect Worklog visibility! Jqls already do not respect it (which is BAD), but luckily only return the total time spent, and not the time per user, which would be a GDPR problem.

            madis002 added a comment - - edited

            I want to log time. Write a comment to the time log that contains a the keyword "BS". Then at the end of the month I want to look how much time "BS" consumed, so I would generate a report where

            worklogComment ~ "BS"

            I would expect to see only the times where I logged "BS", but I will see all of the time I have logged in the issues.

            Lets say I want to add other team members to that report and they did some work on the issue as well, but did not actually have do deal with any of the "BS", but all of their time logged under the issue would also appear in the report.

            madis002 added a comment - - edited I want to log time. Write a comment to the time log that contains a the keyword "BS". Then at the end of the month I want to look how much time "BS" consumed, so I would generate a report where worklogComment ~ "BS" I would expect to see only the times where I logged "BS", but I will see all of the time I have logged in the issues. Lets say I want to add other team members to that report and they did some work on the issue as well, but did not actually have do deal with any of the "BS", but all of their time logged under the issue would also appear in the report.

            Would be awesome to have this feature!!!

            Deleted Account (Inactive) added a comment - Would be awesome to have this feature!!!

            Hi, 
            Is there any update on this worklog by user ticket?

            Namra Rehman Murtazai added a comment - Hi,  Is there any update on this worklog by user ticket?

            Critical for me too

            Deleted Account (Inactive) added a comment - Critical for me too

            • JQL has worklogAuthor which allows user to search by the username that has a worklog on issue.
            • JQL also has worklogDate which allows user to search by the date any work was logged on. 
            • Finally JQL has worklogComment which allows the user to search based on text in worklog comments

            These three options are already present but since they are separate fields they work separately, they filter issues separately. I need something that combines these three. I need to search for issues that has work logged on them between date1 and date2 by specific user(s).

            Since these three JQL fields are already present, I shouldn't be hard to introduce something that combines these.

            Emre Toptancı [OBSS] added a comment - JQL has worklogAuthor which allows user to search by the username that has a worklog on issue. JQL also has worklogDate which allows user to search by the date any work was logged on.  Finally JQL has worklogComment which allows the user to search based on text in worklog comments These three options are already present but since they are separate fields they work separately, they filter issues separately. I need something that combines these three. I need to search for issues that has work logged on them between date1 and date2 by specific user(s). Since these three JQL fields are already present, I shouldn't be hard to introduce something that combines these.

            SonaliH added a comment -

            CASE:
            Step1: When I get ticket->Start Progress
            Step2: When it is in progress, during logging work log I need to put work log based on whether I worked on impact analysis, coding, rework return to dev impact analysis, rework on return to QA coding, etc. How is it possible? I thought to use a description of work log. But then how will I query?
            I would say to have query like:
            Filter for tickets: select tickets_id, Time of workLogDes like "Impact analysis:%",Time of workLogDes like "Coding:%", Time of workLogDes like "Unit testing:%", Time of workLogDes like "Review:%", Time of workLogDes like "Rework Impact Analysis:%" from tickets_table where release =1.1 and project="TEST"
            Why needed:
            1. Workflow will be a common process throughout organization. Hence it is just have status flow like:
            a) Open, In Technical evalution
            b) In Progress, Stoped Progress
            c) Ready for peer review, return from peer review, resolved
            d) Ready for QA, return from QA
            c) Closed
            2. Now in organization we have sub teams like developers, testers etc. Also each team manager need to follow some workflow to get in depth analysis.
            So we need:
            a) Start, Inprogress
            b) Impact analysis
            c) Coding
            d) Unit testing
            c) In peer review
            So for sub workflow if we can filter out from worklog filter tickets then it will give us good solution. I already had one support request: CA-231251. Let us know if any time JIRA plan to implement it.

            SonaliH added a comment - CASE: Step1: When I get ticket->Start Progress Step2: When it is in progress, during logging work log I need to put work log based on whether I worked on impact analysis, coding, rework return to dev impact analysis, rework on return to QA coding, etc. How is it possible? I thought to use a description of work log. But then how will I query? I would say to have query like: Filter for tickets: select tickets_id, Time of workLogDes like "Impact analysis:%",Time of workLogDes like "Coding:%", Time of workLogDes like "Unit testing:%", Time of workLogDes like "Review:%", Time of workLogDes like "Rework Impact Analysis:%" from tickets_table where release =1.1 and project="TEST" Why needed: 1. Workflow will be a common process throughout organization. Hence it is just have status flow like: a) Open, In Technical evalution b) In Progress, Stoped Progress c) Ready for peer review, return from peer review, resolved d) Ready for QA, return from QA c) Closed 2. Now in organization we have sub teams like developers, testers etc. Also each team manager need to follow some workflow to get in depth analysis. So we need: a) Start, Inprogress b) Impact analysis c) Coding d) Unit testing c) In peer review So for sub workflow if we can filter out from worklog filter tickets then it will give us good solution. I already had one support request: CA-231251. Let us know if any time JIRA plan to implement it.

            Hi, this is critical to me, too. Is there any solution in sight? I need a filter showing me all tasks having logged work by me inside a specific project.

            Marcus Noerder-Tuitje added a comment - Hi, this is critical to me, too. Is there any solution in sight? I need a filter showing me all tasks having logged work by me inside a specific project.

            any update on when we can get access to the JQL field for the person who logged work?
            timeSpent tells me how much time was logged, but how can I tell who logged this work?

            Thanks

            Vlad Kaminsky added a comment - any update on when we can get access to the JQL field for the person who logged work? timeSpent tells me how much time was logged, but how can I tell who logged this work? Thanks

            JohnG added a comment -

            This is critical for me as well. I work on many different tasks in the agile environment and I'd like to be able to see all work logs for myself over a certain time range.

            JohnG added a comment - This is critical for me as well. I work on many different tasks in the agile environment and I'd like to be able to see all work logs for myself over a certain time range.

            austegard added a comment -

            I would like to be able to search for an issue that was assigned to one of the members of my team within the past N days. "was assignee" is a start, but I need to limit the time so as not to get issues that are no longer pertinent.

            austegard added a comment - I would like to be able to search for an issue that was assigned to one of the members of my team within the past N days . "was assignee" is a start, but I need to limit the time so as not to get issues that are no longer pertinent.

            aaron n added a comment -

            agreed

            aaron n added a comment - agreed

            When is this feature going to be done? We really need this on our organisation

            Tamara Morillas added a comment - When is this feature going to be done? We really need this on our organisation

            +1 to "@Kelly Dolan"'s comment. We are finding ourselves needing to search for work logs by participants who are not the assignee. We're trying to figure out how to break down our issues so that developers don't need to log work to something that they aren't assigned to but that is becoming very unnatural for us. We need to have a gadget that shows all issues that someone has worked on. We need a search filter that shows all issues to which someone has logged work.

            Christopher Lohman added a comment - +1 to "@Kelly Dolan"'s comment. We are finding ourselves needing to search for work logs by participants who are not the assignee. We're trying to figure out how to break down our issues so that developers don't need to log work to something that they aren't assigned to but that is becoming very unnatural for us. We need to have a gadget that shows all issues that someone has worked on. We need a search filter that shows all issues to which someone has logged work.

            Jon Sword added a comment -

            It would make a lot of sense for us. This is exactly what I was looking for.

            Jon Sword added a comment - It would make a lot of sense for us. This is exactly what I was looking for.

            I would also very much like to see this feature. It certainly would see a lot of use by the dev team I am on.

            Bill Smith added a comment - I would also very much like to see this feature. It certainly would see a lot of use by the dev team I am on.

            I agree this feature is desirable. I consistently get asked by managers about performance of staff members when their annual reviews roll around. The first step is figuring out what they worked on and JIRA is our best source for this information (e.g., issues user logged time to in time period).

            This type of query is available in one of our reports (Time Sheet Report provided by a free JIRA plug-in named "Jira Timesheet Report and Portlet Plugin", see https://plugins.atlassian.com/plugin/details/294). The report is really nice and it has links to each JIRA item the user logged time to during that period. However I'd still prefer a JIRA query in this case because the report is basically a chart of task x hours logged. In my case, I don't need to see a grid that shows individual work logs. I'd rather see the issue navigator view which is much more compact and allows me to see more issue fields at a glance. The JIRA query would also allow me to narrow the search by adding criteria on different fields.

            Kelly Dolan added a comment - I agree this feature is desirable. I consistently get asked by managers about performance of staff members when their annual reviews roll around. The first step is figuring out what they worked on and JIRA is our best source for this information (e.g., issues user logged time to in time period). This type of query is available in one of our reports (Time Sheet Report provided by a free JIRA plug-in named "Jira Timesheet Report and Portlet Plugin", see https://plugins.atlassian.com/plugin/details/294 ). The report is really nice and it has links to each JIRA item the user logged time to during that period. However I'd still prefer a JIRA query in this case because the report is basically a chart of task x hours logged. In my case, I don't need to see a grid that shows individual work logs. I'd rather see the issue navigator view which is much more compact and allows me to see more issue fields at a glance. The JIRA query would also allow me to narrow the search by adding criteria on different fields.

            This is such a fantastic feature to be used by project managers to track the work done by individual developers/testers for last week/month or so. Makes life lot easier and gives a possibility to have nice dashboard gadget to understand progress with one second click instead of asking each individual for several minutes.

            prabhakar reddy darakapalli added a comment - This is such a fantastic feature to be used by project managers to track the work done by individual developers/testers for last week/month or so. Makes life lot easier and gives a possibility to have nice dashboard gadget to understand progress with one second click instead of asking each individual for several minutes.

            Jeff Kirby added a comment -

            The HP/Palm Jira Search Plugin will allow you to search the change history of a Jira issue. It also provides a menu version of JQL to help you with the syntax.

            For example, this screen shot will find all issues where the assignee was changed from 'jeff kirby' to 'matt doar'

            Jeff Kirby added a comment - The HP/Palm Jira Search Plugin will allow you to search the change history of a Jira issue. It also provides a menu version of JQL to help you with the syntax. For example, this screen shot will find all issues where the assignee was changed from 'jeff kirby' to 'matt doar'

            Jeff Kirby added a comment -

            The HP/Palm Jira Search Plugin will allow you to search the change history of a Jira issue. It also provides a menu version of JQL to help you with the syntax.

            For example, this screen shot will find all issues where the assignee was changed from 'jeff kirby' to 'matt doar'

            Jeff Kirby added a comment - The HP/Palm Jira Search Plugin will allow you to search the change history of a Jira issue. It also provides a menu version of JQL to help you with the syntax. For example, this screen shot will find all issues where the assignee was changed from 'jeff kirby' to 'matt doar'

            I would also appreciate such functionality. In addition, logging the time the issue was assigned to each user would be very helpful (note, that the time an issue was assigned to someone is different from the logged work of a participant). We would like to use this, to find out if issues were assigned to users for an unusual long amount of time. And currently there is no way to find this out afterwards.

            Thanks & Cheers, Benjamin

            Benjamin Reitzammer added a comment - I would also appreciate such functionality. In addition, logging the time the issue was assigned to each user would be very helpful (note, that the time an issue was assigned to someone is different from the logged work of a participant). We would like to use this, to find out if issues were assigned to users for an unusual long amount of time. And currently there is no way to find this out afterwards. Thanks & Cheers, Benjamin

            I would be very happy to see this function in an upcomming version

            Manuel Wortmann added a comment - I would be very happy to see this function in an upcomming version

            AvivaY added a comment -

            I'm also looking for this functionality. The request comes over and over from the managers in my company.

            AvivaY added a comment - I'm also looking for this functionality. The request comes over and over from the managers in my company.

            Apologies guys, my mistake. Reopening this issue.

            Mario

            Mario Giacomino [Atlassian] added a comment - Apologies guys, my mistake. Reopening this issue. Mario

            Mario - the participants field does not include those who were involved in transitioning an issue - unless they also left a comment. Therefore, the custom field needs to be improved on or this issue is a valid request on its own right.

            Neal Applebaum added a comment - Mario - the participants field does not include those who were involved in transitioning an issue - unless they also left a comment. Therefore, the custom field needs to be improved on or this issue is a valid request on its own right.

            Hi Jay,

            I am closing this due to a current implementation of a "Participants" custom field. This is a searchable custom field that lists all users who have participated (commented/transitioned/etc.) in the issue. This custom field is part of the JIRA Toolkit.

            Thanks,
            Mario

            Mario Giacomino [Atlassian] added a comment - Hi Jay, I am closing this due to a current implementation of a "Participants" custom field. This is a searchable custom field that lists all users who have participated (commented/transitioned/etc.) in the issue. This custom field is part of the JIRA Toolkit . Thanks, Mario

              Unassigned Unassigned
              3df6e1aa2687 Jay Sellers
              Votes:
              257 Vote for this issue
              Watchers:
              110 Start watching this issue

                Created:
                Updated: