• Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Currently the Issue Type page, https://<instance>/secure/admin/ViewIssueTypes.jspa only allows the edt of an existing issue type or the creation of a new issue type.

      An improvement would be the addition of a copy operation for an existing issue type.

      This would benefit users that have already created a customised issue type that they would like to reuse with some modifications.

            [JRASERVER-32018] Copy/Clone of an existing Issue Type

            ShineyRoshia added a comment - - edited

            Jira

            ShineyRoshia added a comment - - edited Jira

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.

            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

            MikeyS added a comment -

            Elijah, are your fields required in your workflow with validators? If so, you should be able to bypass them with a separate transition that doesn't use those validators to close out the issue.

            MikeyS added a comment - Elijah, are your fields required in your workflow with validators? If so, you should be able to bypass them with a separate transition that doesn't use those validators to close out the issue.

            Elijah added a comment -

            For my situation this would be huge help.
            Here is the situation:
            We have an issue that has many required fields that a user must specify values for in order to continue down the path.
            The problem:
            There are times where the client wishes to close an issue immediately or as I call it Administratively Closed where required fields are not populated.
            The client does not care that the required fields are not populated.
            They do not want any additional information to have to be populated into the fields which would be valid content.
            They want it closed NOW end of story.

            My thinking on this topic is that I we are able to clone the issue in it's entirety then we would be able to mimic the issue and remove all required fields. This would allow us to move an issue when they want it closed over to the clone and then Close the issue.

            Elijah added a comment - For my situation this would be huge help. Here is the situation: We have an issue that has many required fields that a user must specify values for in order to continue down the path. The problem: There are times where the client wishes to close an issue immediately or as I call it Administratively Closed where required fields are not populated. The client does not care that the required fields are not populated. They do not want any additional information to have to be populated into the fields which would be valid content. They want it closed NOW end of story. My thinking on this topic is that I we are able to clone the issue in it's entirety then we would be able to mimic the issue and remove all required fields. This would allow us to move an issue when they want it closed over to the clone and then Close the issue.

            MikeyS added a comment -

            Seems like this would be especially useful for duplicating regular Issue Types as Sub-Task Issue Types.

            MikeyS added a comment - Seems like this would be especially useful for duplicating regular Issue Types as Sub-Task Issue Types.

            Would help a lot.

            Crowdcontrol added a comment - Would help a lot.

              Unassigned Unassigned
              pgreig Paul Greig
              Votes:
              13 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: