Concourse & Jira Cloud Portal
Currently, when a Jira work item is copied or cloned, any linked assets (such as PDM-recommended tools, templates, or automations) do not carry over to the new item — and there is no way to add them afterward.
This results in missing guidance and lost context for copied work items, especially when users reuse activities or templates after a Concourse plan is pushed.
The enhancement would enable assets to be automatically inherited from the original work item or allow users to manually add or re-link them to the copied issue through a supported action.
Allow assets to carry over — or be reattached — when Jira items are copied.
This closes a significant usability gap by ensuring teams don’t lose access to critical PDM content when reusing or cloning work items. It prevents confusion, reduces manual effort, and helps maintain consistency and adherence to delivery standards across engagements.
“When a new activity was a copy and paste… what happened to these assets? Are they coming over or it’s completely lost?”“If it gets copied over, you also replicate or copy over the assets as well… This is a pretty big issue… PMs… how they’re really using the PDM content… If I copy a thing into another, I need to carry it over.”
