Jira Assistant Issues

View #242 on GitHub to know more details

#242 - Worklog entries removed from worklog calendar and report after upload

samsuits commented on Jan 08, 2023

Basic Details

  • Jira Assistan Version : v2.42
  • Browser & Version: Google Chrome Version 107.0.5304.87
  • OS: Ubuntu

Describe the bug Worklog entries getting removed from worklog calendar after upload. This is happening specially with closed ticket. They are getting recorded but not more available to see in the worklog calendar for view. This is affecting worklog report as well. Worklog report not calculating tracking of closed ticket. I understand there is a setting in General -> Worklog -> 'Allow logging work on closed tickets', this is ticked as well. This is happening for both plugin and web version of jira assistant.

To Reproduce Steps to reproduce the behaviour (if applicable / necessary):

  1. Go to 'Jir Assistant'
  2. Click on 'Workdlog Calendar from side menu'
  3. Add a worklog by clicking on calendar. Add a worklog for closed ticket
  4. Click on 'upload' button to upload worklog
  5. The entry will be removed from calendar but it has been uploaded to Jira
  6. The behaviour is same for plugin and web version

Expected behavior The worklog entries should continue to appear on worklog calendar after upload for closed tickets The worklog report should always calculate and report worklog entries for closed tickets

Screenshots image image

shridhar-tl commented on Nov 17, 2022

Hi @samsuits - Thank you for reporting this issue, however, this is not an issue with Jira Assistant, but an issue with Jira indexing.

Multiple users had reported similar issues and every time this issue is because Jira server is not indexed properly. Please ask your Jira Admin to reindex the Jira server and that should resolve your issue. If you still face this issue after reindexing Jira, I will provide you with the steps to debug the issue. But as of now, I am pretty confident that it has nothing to do with Jira Assistant.

Here is one such random issue caused by Jira indexing: #61. There are several more reported so far.

shridhar-tl commented on Nov 24, 2022

Hi @samsuits - Did the suggestion solve your issue?

samsuits commented on Dec 04, 2022

Hi @shridhar-tl Thank you for response. We use cloud version of jira. Will this solution work on cloud version as well ?

shridhar-tl commented on Dec 05, 2022

Hi @samsuits, I believe cloud version would be automatically indexed regularly. So I don't think you will need to/would be able to index manually.

I'm using both cloud version and data center version as well and I don't see any such issues happening. I'm at this point clueless on what is happening. One think you can try is have network tab open before pushing the worklog from calendar and see what is the network requests going on and also see if there are any failures. It should try to pull the worklog for the selected date range and see if JIRA is responding with the appropriate tickets list.

That would be the next step to try. By the way, in first place are you still able to reproduce the issue?

samsuits commented on Dec 05, 2022

@shridhar-tl Looks like the issue is with total number of work-logs jira-assistant can handle. We have some standard tickets to log admin and other common work-logs. One of those tickets has over 20,000 work-log entries. This is beginning of network response of one such ticket.


May be jira-assistant need to limit the response by filtering date-range ?

shridhar-tl commented on Dec 20, 2022

Hi @samsuits, good that you were able to identify the root cause. However using same ticket for longer period is not something which is suggested. Because not just for Jira Assistant, any apps trying to pull the information would put load on the server.

And by the way, unfortunately JIRA does not provide option to pull worklogs only based on a specific date range. We can only filter the issues and when it comes to worklog, comments, change history all that does not have any option to filter data at this point. So we need to pull the entire data and then filter it with date. So as of now there is no way around it.

[Update] - Jira Cloud started supporting filtering of worklogs based on a specific date range for individual issues. Hence my statement above (based on 6 years old knowledge) stands outdated. From v2.44 of JA, started using such filter and now too many worklog in a single issue is no more a problem for Jira Assistant

shridhar-tl commented on Dec 20, 2022

Hi @samsuits - A fix has been provided to solve this issue and is now available in web version. For now to solve this issue, you can use Web version either by visiting https://app.jiraassistant.com or by clicking on "Switch to Web" menu under "WEB" badge on top right corner of Jira Assistant.

In around a weeks time, I will try and publish the updates to extension users.

shridhar-tl commented on Dec 27, 2022

This implementation is done and hence closing this issue. This change is already available in Web version and you would start seeing the changes in Extension and Cloud App once you are updated to JA v2.44.

samsuits commented on Jan 08, 2023

Wonderful. Web version looks good. Thanks for fixing it !!