Repository navigation
feat(tracker): copy issue templates to another project - #11146
Open
MichaelUray wants to merge 1 commit into
Open
MichaelUray wants to merge 1 commit into
MichaelUray wants to merge 1 commit into
Conversation
Issue templates are stored in a single project and the only action available on them was Edit, so a template had to be recreated by hand for every new project. Add a "Copy to project…" action for issue templates. It opens a popup with the existing project selector (excluding the template's own project) and creates a copy of the template in the chosen project, including its child templates, description, priority, assignee, labels and estimation. Component and milestone belong to the source project and are cleared; a task type is kept only when the target project type provides it. Child templates get fresh ids; comments and attachments are not copied. The data mapping lives in a small pure helper covered by unit tests. Fixes hcengineering#5892 Signed-off-by: Michael Uray <michaeluray@users.noreply.github.com>
MichaelUray
force-pushed
the
feat/issue-template-copy-project
branch
from
October 19, 2026 06:42
8e6d455 to
939307f
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #5892
Problem and change
Issue templates are stored in a single project and the only action available on them was Edit, so a template had to be recreated by hand for every new project.
Add a "Copy to project…" action for issue templates. It opens a popup with the existing project selector (excluding the template's own project) and creates a copy of the template in the chosen project, including its child templates, description, priority, assignee, labels and estimation. Component and milestone belong to the source project and are cleared; a task type is kept only when the target project type provides it. Child templates get fresh ids; comments and attachments are not copied. The data mapping lives in a small pure helper covered by unit tests.
Tests
New unit tests
plugins/tracker-resources/src/components/templates/__tests__/copy.test.ts. Checked manually on a self-hosted instance: the action copies a template with its child template, labels and estimation into another project (component/milestone cleared); only projects the user is a member of are offered, none is preselected; an issue can be created from the copy.