Known issues
- 1 List view of a project in Jira
- 2 Edit worklog
- 2.1 Start time of an edited work log changes autmatically
- 2.1.1 Symptoms
- 2.1.2 Cause
- 2.1.3 Resolution
- 2.1 Start time of an edited work log changes autmatically
- 3 Custom JQL (Data Center only)
- 3.1 Returns more results
- 3.1.1 Symptoms
- 3.1.2 Cause
- 3.1.3 Resolution
- 3.1 Returns more results
List view of a project in Jira
Cannot log time from the list view of issues in a project (Cloud only)
Symptoms
If you navigate to Issues in the list view and try to log time by clicking on Log work from three dots near an issue, you are redirected to an empty page with the following error message:
Cause
Unfortunately, the issue is on Atlassian side. This view was created not so long ago, and it looks like some is not loaded on Atlassian side, when you click on Log work.
Resolution
Unfortunately, this issue shold be checked and fix on Atlassian side first. We have asked in the community The button added to web items not working in list ... (atlassian.com)
To get the resolution faster, or if you would like to track the progress, please kindly start watching this question or add your reaction.
Edit worklog
Start time of an edited work log changes autmatically
Symptoms
If a work log is edited, start time is changed even if an actor does not change it manually.
Cause
This problem occurs during periods close to daylight savings time.
Resolution
We strongly recommend to use GMT Offset and set time as GMT+N in user’s profile.
Custom JQL (Data Center only)
Returns more results
Symptoms
If you search for issues, where worklogs were added to a specific date (chosen data range contains one day only), you may get extra results.
sWorklogDate >= 2023-07-11 and sWorklogDate <= 2023-07-11
sWorklogDate = 2023-07-11
If you create a complex JQL with multiple functions, you may get extra results.
Cause
Sometime expressions return more search results as expected, as Jira considers them all as correct results.
Resolution
Unfortunately, as it correlate with current Jira logic, there is no workaround or resolution at the moment.