Epics are not shown neither in the new nor in the old worklog report

shridhar.tl@gmail.com

Jira Assistant Issues

View #250 on GitHub to know more details

#250 - Epics are not shown neither in the new nor in the old worklog report

Ernte1893 commented on Jan 03, 2023

Checklist before you being

I am sure that I am already using latest version of Jira Assistant
I had verified that, no similar issues are already reported in issue tracker
I had tried reproducing this issue with with Web version of Jira Assistant to ensure that this issue is not recently fixed and yet to be published
I had verified that, my query is not answered in FAQ section of website
I had verified that, my issue is not listed as known bugs in website

How do you use Jira Assistant?

Browser extension

Are you using cloud version of Jira or self hosted (data center / server) of Jira.

Self hosted (datacenter)

Version of Jira Assistant

v2.44

What browser are you using?

Firefox

What OS are you using? You need not disclose this if you feel it is irr-relevant for your issue.

Windows

Bug Description

When enabling the optional option in the worklog report to also show the epic field, the epic column is shown, but remains empty. All tickets are shown, but the epic connection is not visible.

Checklist before you submit

I have ensured not to paste any confidential information like Jira url, Mail id, etc.
I have verified my browser console logs and added necessary details (if required)
I have added required screenshots if the bug is related to UI (as necessary)

shridhar-tl commented on Jan 03, 2023

Hi @Ernte1893 - This is partially a known issue. In General Settings -> Default value tab, you have a field where you need to select Epic name field. Once you navigate there it would auto select Epic Link as the value. You can change the field to be used (if required), then you can once again navigate back to report and you will see the Epic link value is populated in both the report. By default epic link should be the correct field, however in some instance of Jira it is customized and that is the reason it is necessary for the user to change it from this page.

However, I just realized that this field is not being populated in New Worklog Report, while using timeframe as sprint. This would be fixed in upcoming release in couple of week.

shridhar-tl commented on Jan 03, 2023

This issue has been fixed and would be available in JA v2.45 once published. It would immediately be available in web version.

Closing this ticket considering this issue is resolved.

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.