"Issue Key" field for Work Logs unresponsive to some search terms or issue types

[Mike Premo]

Using the "My Work" worklog calendar API:

For example, I have two projects "SBIR" and "Linx".  When I type in "Linx", I get a list of 17 issues that I could log work to.  When I type in "SBIR" only one issue shows up.  My coworker types in the same "SBIR" and gets no issues to show up.  My other coworker types in "SBIR" and gets about 10 to show up.  We're all using the same JIRA server instance and projects...

When I type in Linx-83, which is a sub-task, it does not appear in the search window to choose from.  This is another related issue (sub-tasks don't show up in the search window).

Something appears wrong with how the Issue Key field is being used to search through the database for possible issues to log work against.  This is a major pain point since it requires us to go find each issue name or log work directly to the issue (not using your calendar at all).

[Volodymyr Krupach · Accepted solution]

Hi Mike,

Just released version 2.4 that includes fix for "Issue key auto-complete" problem.

Please be aware that during next 2 weeks I will be merging Server and Cloud versions of the Work Calendar. This requires recreation of the Work Calendar marketplace listing. Since it will be a new marketplace listing, you will need to uninstall the current version and install the new one. I will contact you with detailed instructions.
CommentAccept answerEditDeleteConvert to comment

[Mike Premo]

Thanks! I updated and tested this out. Filtering appears to work great, with exception for the sub-tasks. These still do not show up in the Issue Key Filter. Thoughts on that?

[Volodymyr Krupach]

Mike, > with exception for the sub-tasks Will correct it tomorrow.

[Mike Premo]

*Like* or *Up-Vote* :-)

[Volodymyr Krupach]

Mike, please upgrade to the latest version. Sub tasks should appear in auto suggest box. Thank you for reporting the problem!

[Mike Premo]

Works! Thank you!!

[Volodymyr Krupach]

Hi Mike!

What filter values do you have on the left?

Maybe Projects are switched and Linx is unchecked. Or Maybe you picked a filter that eliminates Linx issues (and you colleague has another filter so for him/her one issue is shown).

Subissues should be shown as well. Only restriction is the current criteria you configured through Projects or Filter selections.

[Mike Premo]

We checked this first and everyone verified that they are using "All Issues" as the chosen filter. Not able to observed Sub-issues with this filter selection.

[Volodymyr Krupach]

I assume that issues are not restricted by security and users can browse them on the issue search page. Right? Could you please launch Chrome devtools or FireBug (F12 to activate any of them) and type "Linx" in the Log Work dialog and send the logs to me: https://productforums.google.com/forum/#!topic/chrome/sHrhpCLJ87I

[Mike Premo]

No restrictions via security or users to certain issue types. Can easily use the Atlassian JIRA search field to find the issues in question, just not from the work calendar. Mine doesn't work well for the SBIR project, so I did what you asked except used "SBIR" in the Log Work dialog. I had Chrome devtools open, but am not sure what window you would like as the "logs". Could you please send a screen-shot or otherwise provide steps to provide you this information?

[Volodymyr Krupach]

Mike, I reproduced the bug in my JIRA and after some digging I found that it's caused by known bug: https://ecosystem.atlassian.net/browse/ACJIRA-314 Could you please vote for the bug to persuade atlassain to fix it ASAP. Anyway I will need to create a version of the plugin that ignores the criteria on the left panel when autocompleting issues. I will do it on June 17th, when I am back from vacations.

[Mike Premo]

Thanks for reproducing! I will vote for the bug and look forward to a potential fix after you enjoy some vacation :-)