Uploaded image for project: 'Atlassian Marketplace'
  1. Atlassian Marketplace
  2. MP-70

Allow site admins to disable JIRA Labs feature during User Creation

    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      • As of now, users are only able to disable this feature from their profile after their account is created
      • Admins would like to have a feature to flag this off during the user creation process

      Suggested Solution

      Include a checkbox in the Invite User form to enable / disable JIRA Labs feature

      Why this is important

      The old view shows pretty much every information needed in one place. Until the new issue view is fully implemented, admins would like to have the option to toggle it on or off

      Workaround

      Have the user disable it from their profile after the account creation is successful

            [MP-70] Allow site admins to disable JIRA Labs feature during User Creation

            Rabbit added a comment -

            In addition, for QA testers using Zephyr, they won't be able to see test steps until the new UI is turned off. This is extremely confusing for new users and wastes a lot of their time.

            Rabbit added a comment - In addition, for QA testers using Zephyr, they won't be able to see test steps until the new UI is turned off. This is extremely confusing for new users and wastes a lot of their time.

            For people who run a tracking system you really need help on managing your own.   

            This is the bug that should be open:  JRACLOUD-67328  this one really should be closed with a comment linking it to the original bug that is asking for the same thing.  Now you have three bugs, your users really don't know which to vote for, multiple comments asking for updates, and you've got three open bugs in your system instead of the one that is actually required.  Our backlog would become a monster if we did the same thing.

            Mark Thompson added a comment - For people who run a tracking system you really need help on managing your own.    This is the bug that should be open:   JRACLOUD-67328   this one really should be closed with a comment linking it to the original bug that is asking for the same thing.  Now you have three bugs, your users really don't know which to vote for, multiple comments asking for updates, and you've got three open bugs in your system instead of the one that is actually required.  Our backlog would become a monster if we did the same thing.

            Any update or is this the standard Jira avoids the issue until it goes away?

            Mark Thompson added a comment - Any update or is this the standard Jira avoids the issue until it goes away?

            Alex added a comment -

            Any update?

            Alex added a comment - Any update?

            Alex Silva added a comment -

            Good Morning, We know something about how to disable jira labs by default. The experience is very bad. Grouping all the fields on the right side is horrible. also some plugins are not seen correctly, it seems incredible that this enabled by default for new users.

            Alex Silva added a comment - Good Morning, We know something about how to disable jira labs by default. The experience is very bad. Grouping all the fields on the right side is horrible. also some plugins are not seen correctly, it seems incredible that this enabled by default for new users.

              Unassigned Unassigned
              adanial Ahmad Danial (Inactive)
              Votes:
              51 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated: