/rest/api/2/search?fields=project&maxResults=1000&jql=worklogDate >= "2019-04-07" and worklogDate < "2019-04-10"
Adding the above to my Cloud Jira domain returns Issue Types of Task, Bug, and Sub-Task. It doesn't include Story or custom fields. I confirmed this by creating a "Bug" issue, logging work, and seeing it appear in the results. Then I changed the Issue Type to "Story", refreshed the results, and it was no longer included.
Anyone have any insight?
EDIT: In looking at this some more, it appears adding a "worklogDate" term to the JQL is what results in the "Story" and custom issue types not being included. HTH
Atlassian support resolved the isuse. They provided the following information:
We've checked each project's field configuration and then tried to use the hide/show to re-insert them into the field scope. It appears that these fields had a missing field scope, the workaround, provided by the development team, is to re-insert these fields in the field scope using the hide/show option.
Hello Jim,
I hope you are having a nice day.
My Stories are been properly displayed when I run the REST API search you mentioned on my personal Cloud site.
That been said, please check the following steps to troubleshoot the problem:
- When you run the search in the Issue navigator directly, it returns the Stories it should?
- The Stories you are expecting to return in the search should be properly configured with a Time Tracking estimation and with some work logged in the time range you specified in the query. Can you please double-check that the issues match both conditions? Usually, Stories are measured in Story Points, which is not related to the Worklog_date field.
- Double-check in the work log tab of the issues (Old Issue view) that the date is a day between the two dates you added in the query
- Is the Time tracking field properly configured in the Project Screens for the Story issue type?
If the steps above don't help, please provide us a screenshot with the time logged for the Stories that should be returned in the query.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your reply. Atlassian support resolved the isuse. They provided the following information:
We've checked each project's field configuration and then tried to use the hide/show to re-insert them into the field scope. It appears that these fields had a missing field scope, the workaround, provided by the development team, is to re-insert these fields in the field scope using the hide/show option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.