Tracked time being overridden

Jira Assistant Issues

View #42 on GitHub to know more details

#42 - Tracked time being overridden

jakul commented on Aug 01, 2018

Hi,

Thanks for making this extension @shridhar-tl , it's the best way I've found to log time to JIRA. However, I have just found a bug.

I track time against tickets in multiple batches - e.g. I'll record on worklog entry of 4 hours against a ticket and then another of 1 hour. When I view the ticket in JIRA it only shows the "time spent" as being 1 hour though, not the 5 hours I expect.

Here's what Jira Assistant shows: captura de tela 2018-07-10 as 14 57 53 1

And here's the ticket in JIRA: ticket_in_jira .

shridhar-tl commented on Jul 25, 2018

Hi @jakul , Sorry for the delayed response. I have been bit overloaded with some work and so not able to concentrate on fixing these issues. I will try to fix this and other issues in a couple of weeks. Till then please bear with me. Thank you for being patient so far!!

shridhar-tl commented on Jul 30, 2018

Hi, this issue is actually with the limitations in Jira itself. Jira was not able to handle batch concurrent worklog update for same ticket. So it was not able to calculate the time properly. One such similar issue is discussed in the below link. I will have to change the worklog upload to sequential instead of concurrent upload to fix this issue. But it will obviously increase the time to upload the worklog if their are lots.

https://community.atlassian.com/t5/Jira-Software-questions/Time-Tracking-quot-Logged-quot-shows-wrong-value/qaq-p/647203

shridhar-tl commented on Aug 01, 2018

Hi @jakul, This issue has been resolved and is available in latest update. Please check and let me know if this issue has been resolved for you.

jakul commented on Aug 01, 2018

This works for me! Thanks for fixing it and keep up the good work!

Latest updates

27-Nov-2023 - Change in permissions for JA

In upcoming version (v2.58) of JA, by default, permission to access Cloud instance of Jira would be added. This would let the users to integrate with Cloud instance of Jira without prompting for permission at the time of integration. Hence for Chrome users, once the extension gets updated, it would get disabled due to change in permission. You can enable it again from Extensions page. However, for Firefox and Edge, extension already have access to all the sites (though it doesn't really need) which would be narrowed down only to atlassian.net which would be a security improvement.

03-Jan-2023 - Auto update would take time

Jira Assistant is now updated in phased basis to avoid any breaking changes impacting all users. So it may take long time before your extension gets updated. If you want to manually update it immediately, just navigate to "chrome://extensions", turn on "Developer mode" from top right corner and click Update button. Then you can turn off dev mode.

20-Dec-2022 - Available as App for Jira Cloud

Jira Assistant can now be installed within your Jira Cloud as an App. Once installed, this would be available for all your Jira users. Visit https://www.jiraassistant.com to know more.

26-Jul-2022 - Introducing JA Web

You can visit https://app.jiraassistant.com to use or test upcoming features of Jira Assistant. Contribute in testing JA by switching to Web Version. All the fixes and new feature updates would be immediately available in Web version of JA. Later, stable updates would be pushed to Extensions.

🟢