Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-45840

Change wording of "Shared Configuration" feature

    XMLWordPrintable

    Details

    • UIS:
      1
    • Support reference count:
      4
    • Feedback Policy:
      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.

      Description

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

      Original description:

      When creating a Project using the Create with shared configuration button on the Create Project screen, it could give the user the impression that the projects would have an ongoing connection of some kind, such as with JRA-7020.

      However, the feature currently just "clones" the existing configuration. Because of this, it would be nice if the wording changed.

      The button could change from Create with shared configuration to Clone Existing Project Configuration (similar to cloning plans/deployments in Bamboo).

      In addition, the title of the next screen "Create with shared configuration" would read "Clone with existing project configuration".

      In addition, the description of the next screen "Select the existing project that you'd like to share configurations with." would read "Select the existing project that you'd like to clone the configuration of."

      In addition, the warning message "When a configuration is shared with several projects, it means that any changes made to the configuration will affect all the projects." on the next page could say "While project configuration schemes are shared between projects, it means that any changes made to the configuration will affect all the projects."

      If this feature ever becomes similar to JRA-7020, this could be rolled back.

       

      Update

      Since the word "Clone" implies doing something that the functionality does not really provide, the suggestion to call it "Shared Schemes" or "Use existing Schemes" instead of "Shared configuration" makes it much clear to understand what exactly will be done. 

        Attachments

        1. Configuration.PNG
          Configuration.PNG
          4 kB
        2. SharedConfiguration.PNG
          SharedConfiguration.PNG
          8 kB
        3. TitleDescription.PNG
          TitleDescription.PNG
          9 kB

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              developers2 Swift Capital
              Votes:
              47 Vote for this issue
              Watchers:
              27 Start watching this issue

                Dates

                Created:
                Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1m
                  1m
                  Remaining:
                  Remaining Estimate - 1m
                  1m
                  Logged:
                  Time Spent - Not Specified
                  Not Specified