Versions Compared

Old Version 5

changes.mady.by.user JuliaW (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Betsy Walker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Global administration

Once the Delegated Administration for JIRA add-on has been installed and valid license supplied, you can access the Global Configuration screen in the JIRA Administration area.

From this screen, you can set permissions for who can change schemes and which schemes can be handled by non-JIRA administrators. This includes:

  • Permissions scheme
  • Notifications scheme
  • Issue Type scheme
  • Issue Type Screen schemes
  • Workflow scheme
  • Field Schemes
  • Issue Security schemes

Image Removed

Who can you delegate administration to?

For all of the types of configurations you are able to delegate, you can set the permissions to reflect the following:

  • None - This will disable the switching for this particular scheme
  • Project Lead only - Only the single user that is designated as the project lead on the project will have access.
    • Users with

    Project

    admin permissions - If somebody has access to the project

    administration

    functionality (version, roles and component editing for example) they will have access to this feature.

    For permissions and notification schemes, an additional permission type allow users to duplicate their current permission or notification scheme and then maintain it themselves.

    Scheme selection

    For each type you can select which schemes are available for project administrators to select from:

    • None - This will disable the switching for this particular scheme.
    • All items - This will allow users to select from all of the schemes in your instances
    • Exclude certain schemes - You're able to select which schemes should not be available for users to select from.
    • Only specific schemes - Select the specific the schemes that should be available to project administrators to select from.

    Available Groups

    For permissions and notification schemes, the global administrator can manipulate who can select groups to be included when these are duplicated and maintained on a project basis. The same setting as above are used.

    Project administration

    Once a user has been given permission to a Delegated Administration component the "Delegated Administration" link is shown on the Project administration page.

    Overview

    Info

    Currently only Permissions and Notifications supports "forking" (maintain their own local version). More will be added in the future.

     

     

    On the project's "Delegated AdmisnitationAdministration" screen, each of the areas available scheme type is shown with links options to Change or Fork an item the scheme. If a user doesn't have the proper rights for a certain component (or it has been disabled) it is not shown on this page.

     

    For each item a user can select to:

    • Change - allows users to switch the scheme to another scheme
    • View History - Allows for quick reversion to a previous scheme.
    • Fork the scheme (only available for Permissions and Notification schemes) - Clones the scheme and allows for local editing of it.

    Duplicating and maintaining Permissions and Notification schemes locally

    If a user elects to Fork a permission or notification scheme, they're presented with a dialog for a new name.

    Once this has been done a new Edit option appears. From this the user can add permissions or notification targets.

     

    At any point they can revert the forked scheme back to the original. This will then flip it back (if possible) and delete the forked scheme.

     

    Changing schemes

    For any project a user can select a different scheme by clicking "Change". Once this is clicked the user is shown the current scheme. At this point by clicking "I'm sure" the dialog is updated with the list of schemes that can be changed to. Simply select the scheme to change to and the change is done.

    Info
    titleWorkflows

    For the workflow schemes, the migration requires the user to select the appropriate statuses to migrate things to. 

    Image Added

    Rolling back changes

    At any point a user can click "History" to see what changed in the project in regards to a particular scheme type. From here they can select to revert or "rollback" to a particular state.

    Info

    In the cases where a scheme is no longer found (an administrator removed it from the system or it was a forked permissions, notification scheme that was unforked and thus deleted) the system will say "Unknown scheme".

    Image Added