When converting an issue to an epic (and reverse) bring the Design Tab repo contents over
Problem to solve
As a Designer or Product Manager when I convert an issue to an epic, I want the Design Management content to come with me to the new epic.
Intended users
- Parker (Product Manager)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Presley (Product Designer)
Further details
- Note, this issue is blocked by the ability to have Design Management on epics: #202150 (closed)
- It's important to be able to convert between different types of objects and
Issue -> EpicandEpic -> Issueis part of the efficiency when rearranging a backlog. Right now you lose your designs when you make the conversion.
Proposal
TBD
Documentation
- Ensure docs for migrating issues to epics mentions that Designs will come with
What does success look like, and how can we measure that?
- Do we have a way of tracking that these were created via conversion from issue?
- Would it make sense to have your repo come with and not remain on the issue? <-- @jareko thoughts?