Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to update time spent on subtasks quicker?

Hello All,

I am wondering it if it possible to add a time stamp to the menu "..." area to allow assignees a quicker way to record their time without going into each subtask?

Capture.PNG

2 answers

Digging into this a little deeper, I noticed there is a "Log Work" option. This still takes you into the subtask and takes additional time I was hoping to save. I am looking for a feature that allows you to input time right from the Assigned to Me table.

0 votes

Hello @Garret Heusinger ,

An option was recently added to Jira Server (Tracked here) However, it has not yet made it to the Jira Cloud platform so there is not currently a bulk edit option for the log work operations in Jira Cloud, and the feature to implement this in Jira Cloud is being tracked at the following link:

The current recommendation is to bulk edit worklogs via the JIRA REST API and the Project manager Dave Meyer left a detailed example in this comment on how to implement this via an API update:

Noting:

You can get a set of issues by calling the {{/search} endpoint with the ?jql= query parameter and a URI encoded string of JQL, e.g.

https://baseurl.atlassian.net/rest/api/2/search?jql=project%20%3D%20DEMO%20and%20%22text%20field%22%20~%20%22asdfasdf%22&fields=worklog

In this example I also passed worklog in the fields expansion to expand the worklog objects in each issue that is returned.

Each issue object contains a self URL that is the REST representation of the worklog, like this:

"worklogs": [
                        {
                            "started": "2016-09-07T00:00:00.000+1000",
                            "self": "https://baseurl.atlassian.net/rest/api/2/issue/10103/worklog/10300",
                            "updated": "2016-09-07T23:59:56.722+1000",
                            "issueId": "10103",
                            "id": "10300"
                            ...
                         }
               ...
            ]

You can then call the update worklog REST API to change the remaining estimate, like this:

https://baseurl.atlassian.net/rest/api/2/issue/DEMO-4/worklog/10300?adjustEstimate=new&newEstimate=50m

by using the adjustEstimate and newEstimate query parameters. In case I changed the new estimate to 50 minutes, but you could easily provide "0" as well.

The workaround is to write a script to make the initial REST API call to get the worklogs, parse the response, and then make each individual worklog update request.

Hope this helps.

Dave Meyer
Senior Product Manager, JIRA

Also, make sure to drop a vote on the request to help track continued interest and influence a bump up for the priority for the cloud version of this feature as covered in the Implementation of New Features Policy .

Regards,
Earl

Thank you, Earl!  How many votes does it take before the request is implemented?

Hello @Garret Heusinger ,

There are a lot of factors considered for new features and Votes are not a direct 1 to 1 association for what will be considered for implementation but the Votes and user comments, especially comment with feedback highlighting the impact the feature would or could have (aka the mentioned "User Stories" in the linked material) are two of the primary factors used to influence the process for moving a new feature into development and give the project managers insight on what exactly the end-users need within the products.

Do note that the feature is already a highly voted on request, but not on the roadmap at this time as other features took priority with higher user impact levels, so it is currently on the waiting list for future consideration.  With this as the case influence from continued user feedback is really helpful to push it forward.

The Implementation of New Features Policy mentioned above discusses the process in more detail for the overall factors considered, and there are additional discussions on this at the following community thread about the decision making process:

Regards,
Earl

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you