...
| Info | ||
|---|---|---|
| ||
Level: INTERMEDIATE |
...
To solve this problem we offer a solution that use two of our apps: Power Scripts Scripts™ for Jira and Power Actions Power Actions™ for Jira.
The Solution is exemplified on a Jira 5.2.1 environment. In order to resolve it you have to have administrator rights.
Step 1
Create a new Power Actions Actions™ custom field:
- Go to Administration -> Issues -> Custom Fields and click the link
- Click the Add Custom Field button
- Select the Power Actions Actions™ Custom Field and click Next
- Name it "Disable" and set the desired project you want to lock during the edit process, as shown in the picture:
- Set your Power Actions Power Actions™ Custom Field to be visible on all the screens:
...
- Go to Edit Buttons link on the Configure Blitz (Power) Action Custom Field page. As in the previous the step.
- Press the Edit Screen Script in on the Lock button.
...
Step 3
Now we have to make the SIL SIL™ script that will do the disable operation during the edit.
- Go to Administration >> Plugins >> Kepler General ParametersAdd-ons >> cPrime Tools
- Go to SIL SIL™ Manager tab
- Create a new SIL SIL™ script named "Lock.sil" by clicking on the Show Unused button.
- Select the folder you prefer and click New. Choose File and enter the "Lock.sil" name.
- Enter the following code in the ""Lock.sil":
...
The rowForcustomfield_10300 element represents the custom field ID for the Blitz -(Power) Action Custom Field you have created in the First Step. In fact you only have to replace the number with the ID you have.
- Add the first SIL SIL™ script as a hook on the project you desire.
- Go to Live Fields tab.
- Add a new configuration by clicking the "Add configuration" button.
- Name it whatever you like.
- Add the Lock.sil script you have just created on the SIL SIL™ File box.
- Press Add button.
- Associate this configuration by pressing the Associate link.
- Select your desired project and click the Associate button.
...
This is all. You can now test it by opening two different sessions with two different users and try the lock and unlock buttons.
See also
- Disabling inline edits in Jira
- Forbidding users to create some issue types
- Hide fields from users not in a project role
- Limit Number of Characters in Text Field
- Locking Issues
- Making an issue read-only
- Require an issue to have attachments
- Require User to Log Work Before Transitioning Issue
- Restrict issue type availability by user
- Restrict workflow based on status of dependencies
- Validator for component lead