Field Configuration scheme should show only the screens applicable to the project

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Won't Fix
    • Component/s: None
    • None

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

      When trying to separate projects into using a separate scheme for everything, as a user/ jira administrator I find that th field configurations and field configurations schemes by far the most confusing element possible .

      What really throws me off is the screens that I see in the new project I am in process of creating!

      When I am looking at the new field configuration which is affected only to my new project, which has also a unique screen scheme with 1 single screen affected, I am seeing the multitiude of screens which are only relevant to other projects and even sometimes to some issue types which I do not have in this project.

      This is extremely confusing and even scary at first and even distracting.
      i.e I have to convince myself that the screens that appear in my brand new spanking Field configuration have no effect and that the things I do here will not affect the other field configuration.

      To relate my user experience, even after a few months of working extensively on configuring our JIRA for 3 different Projects, I find the 'multi project jira' really hard to configure.

      As another comment I'd suggest to have some kind of a new project creation wizard which could really simplify just how "separate" do you want this project to be from others (in terms of sharing or not the schemes with them), preferably in one or a handful off screens.

      Right now I'm dreading the day when I'll start configuring my next "separate" project - I'll need to create 8 new schemes and several new configurations and go back and worth between System\Issues and Project\Administration to affect newly created schemes.

      Besides the wizard, there should be a really quick agile option create me a totally separate project with totally separate schemes and configs taking by default the name of the project so I do not have to create and type Project X scheme 10 times...

      this is a major need, for I'd love to just create this totally separate project and just hand it over to a team leader so they configure to their heart's content and I would not have to worry that they mix up something in my other schemes because they forgot that they're sharing them with my other projects...

            Assignee:
            Unassigned
            Reporter:
            Gregory Demotchkine
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: