in order to maintain history and traceability in our development process, I’d like to generate evergreen links to branched designs that are then used in Jira and other documentation tools. are there limits or performance concerns that could prevent this from being feasible long-term?
Question
Branch limits
Hi @John_Sellars1, Thanks for reaching out about this!
I tested this using the “Copy link” option from the “Branches” modal and it seems the file exists unless it’s been manually deleted after archiving.
However, we previously found that querying archived files wasn’t supported. As things might have changed since then, please let us know if you need to use API with archived branches. We’ll check with our team and get back to you with current situation.
Please let us know if I overlooked anything and if anyone else in the community has any insights or suggestions, please feel free to share them here.
Thanks again for reaching out!
the process we’ve established that seems to be working well so far:
- create branch for design exploration and approval
- when design is complete, merge the branch
- generate dev mode links from merged branch and add them to Jira
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.