JPD access level for linking tickets

[Sufian Siddiqi]

If I wanted to link a jira issue to a particular JPD idea, I can associate the two together, but we've noticed that this linking capability is currently not allowed for contributors. 

Example: We have a jira project that tracks our UX team's tasks. If they wanted to associate one of their tasks w/a JPD idea they are unable to do so. 

Is there a plan to extend the linking capability to users with contributor access? 

[Peter James · Accepted solution]

Well that's weird. It has just started working!

Perhaps the Jira angels were watching this community board and fixed the issue in real time :D

[Omer Meshar]

@Peter James I just tried it out myself, and it worked, including setting the hyperlink field:

[Chris Timms]

Hi @Peter James

I have a rule I used pre-template that works the same way. I don't have a solution to your issue but I can validate what you have set up should be working.

Does your automation actually create the confluence page and add the comments? Or is it only adding the URL to the JPD issue that fails?

[Peter James]

The automation creates the page from the template just as I hoped - although it doesn't add the labels - would love an answer to that if anyone has one!

The addition of the comments works just as I expected and the value from {{createdPage.url}} is a valid url.

It is just the editing of the hyperlink field with the url that does not work. It doesn't fail - the audit log says that it was successfully run, it is just that the field appears to still be empty.

When I first tried to set the field with just the value {{createdPage}} the rule step did fail - as noted in the audit log - since the value was not a valid url and so not a valid value for a hyperlink field.