I want to restrict to edit the "Summary" and "Description" fields for automatically created issues

Kumar_ow8zf3

Hi Team,

 

I have an project in that some Tickets(issues) are created automatically through Phantom by the user  "Automation"(reporter) here the tickets that are created automatically by the user automation as reporter i want to restrict the permission to edit the "Summary" and "Description" fields for that auto created tickets. 

the only manually created ticket have permission to edit summary and description fields.

Can you please suggest me regards this.

 

Thanks,

Phani

Gundlupet Sreenidhi

There are a couple ways you can achieve this:

Lets assume you are working on issue-type STORY

Option A: As Nic suggested, create a separate screen for the Edit.

1. Go to Administration --> Issues --> Screens

2. Create separate screens for how the STORY should look like during Create, Edit and View. 

i.e: You will be creating 3 different screens STORY - Create, STORY - EDIT, Story - VIEW

in each of these screens, only add the fields that should be available in those actions. 

In your example:

The STORY - create screen will have the summary and description

The STORY - Edit screen will not have the summary and description

The STORY - view screen will have the summary and description

3. Now go to screen schemes and create a story screen scheme

4. Here Map the actions: Create, Edit and View to the respective screens.

5. Go to Issue Type Screen Scheme and Map the STORY issue type to the screen scheme created above. 

You are all set. 

Now when creating the STORY, the summary and description can be entered. However, if you want to edit is will not be available to edit. 

Note: Care should be taken to put the correct details in the summary and description while creating the STORY. You will not have an option to edit them later. This impacts all issues of type STORY.

 

OPTION B: Using Behavior to control visibility and / or edit-ability

1. Go to Administration --> Add-ons --> Behaviors

2. Create a new behavior (Lets call it story behavior)

3. Create an initialiser.

if(!getFieldById("reporter").getValue().equals("automation")){
    getFieldById("summary").setReadOnly(true)
    getFieldById("description").setReadOnly(true)
}eles{
    getFieldById("summary").setReadOnly(false)
    getFieldById("description").setReadOnly(false)
}

4. (Optional) You can also add the Summary and description field to the behavior and make them read-only as shown in this example. You can even set conditions for when this should apply.

5. Map the behavior to your project and Issue type.

 

Now, every time the issue screen is opened for that project (either, create or edit mode) the behavior functionality will activate. 

Note: the behavior functionality is written to allow edit only for the automation user. All other users can only view the summary and description. You can modify this per your needs.