Jira integration is not sufficient
Now I can only link a full prototype / design spec to a jira issue.
Our workflow is to (deep)link specific screens from that prototype to a single ticket as the scope of the issue is only a part of the prototype.
Or is there a workaround?
This is an important feature to make the Jira integration useful for us.
I'm using Jira Server in my organisation.
Anders Remien Hansen commented
I came here as I've just installed the Adobe XD integration to Jira and was completely puzzled to learn that it links the entire prototype.
Our adobe XD files might have 120 or more screens. In Jira an issue is typically relevant to 1-3 of those screens. Linking to the entire prototype is not very useful for developers, as they have to go figure which pages are relevant themselves. For now this is a minor upgrade compared to simply posting the share link as a comment.
My expectation was that I would be able to specify which screens are relevant for the given Jira issue.
Another limitation is that there can only be 1 link shared for file. Since I have to specify view setting, I can't have both a "Development" and "Presentation" link at the same time. This is a limitation, as I'll like to be able to share it with developers but sales people at the same time. This is related, but another issue than what was stated here initially.
Axel Hermes commented
We have also the request in our team to limit screens shown in a link (not just for Jira) to a specific range of screens.
Reason is that it is sometimes hard for developers or stakeholders to understand where the boundaries of things to look at is.
Currently it is in discussion if we need to separate files to create mini-prototypes focussed on a specific ticket. Which has other disadvantages.
Hi, after the June update, is it still not possible to target a specific screen of the specs?
Linking the full prototype to a single ticket doesn't fit the workflow. The scope of a ticket is not a full prototype, but rather one or two screens of that prototype.
I don't understand why I'm the only one facing this problem with the current workflow.
Thanks for the info!
no they have full access to the prototype but I want to link to the correct page.
Now I'm sharing the deep link in the jira description field.
I don't have a use case where the access to the rest of the prototype is restricted.
Siddharth Arora commented
Thank you for sharing your feedback. We would like to better understand your use case. Do you want to just share a specific portion of your design/prototype in Jira and not give the collaborators the access to rest of your published prototype/design spec?