Issue link in timesheet gadget opens confluence instead of jira
Didn't find this kind of issues in the change log of the newer version since 3.0.51
Our Version: 3.0.51
Usecase:
- timesheet report gadget (using it in confluence)
- Grouping by epic link
- when clicking the epic link a non-existing confluence page is opened and not the jira issue link
incorrect: https://confluence-server/browse/PROJECT-xxx correct: https://jira-server/browse/PROJECT-xxx
Comments (11)
-
-
reporter Hi Andriy,
we start using the timesheet plugin intensively at the moment for a customer support project. I can't compare it to a previous version.
I don't have stories in this project. So I can't check at the moment.
Regards Martin Kellner
-
Hi Martin,
But gadget shows some issues with epic links, right? So could try to embed such an issue in a confluence page, incuding Epic Link field, and see it it's correct there? I believe there should be a macro for this. E.g. https://confluence.atlassian.com/doc/jira-issues-macro-139380.html
Thank you.
-
reporter Hi Andriy,
yes of course ... if I insert the jira issue macro in confluence and filter "issuetype in (epic)", the result is a list of epics and they link to the jira server and not to the confluence server.
regards Martin Kellner
-
-
reporter Ok .... the Epic Link is displayed as a static text and not as a link. Some kind of workaround ;-)
-
Well, if it satisfies your needs, in gadget you may try Epic Name or Epic/Theme instead of Epic Link.
-
reporter I don't think that it would work. Because grouping is done with the epic link field which is set in the issues that are linked to the epic. Epic name is only set in the epic itself, isn't it?
-
There is special logic in plugin to take epic name from related epic, i.e. it traverses through sub-task to task or story then to epic, and takes name from it.
-
reporter Special logic ... ok ;-) I will use it as a workaround. You should keep it in your backlog if things change and you are able to fix it.
-
- changed status to on hold
- Log in to comment
Hi Martin,
Do you mean it worked before?
Looks like it's not feasible to fix, because of using JIRA FieldLayoutItem to generate html for custom fields like Epic Link field, and it apparently generates relative URL.
Could you possibly try if a Story shown in Confluence somehow, has correct link to Epic?
Thank you.