How to stop people from changing the summary of a subtask?

[Md_ Abrarul Huda]

When I create a new jira ticket, I'm also automatically creating a few subtasks which are mandatory to complete.

But not all the subtasks are mandatory for all tickets, which is why there is a "Not required" step in the workflow as well. But track needs to be kept that the specific subtask is there, required or not.

But the team is misunderstanding sometimes and rewriting the summary for the subtask to one of their ongoing deliverables. How can I stop this from happening?

[Trudy Claspill]

Hello @Md_ Abrarul Huda 

Jira does not native support a permission specific to editing the Summary field. 

What type of Space does this concern? Click the ... button next to the Space name in the navigation panel on the left. Tell us what the last two lines in the pop-up are. Both lines are important. They will say something like:

Software space

Company-managed

That will help us advise you on your options.

It may be possible to do something natively, but would require having those subtasks created as a unique work item type, which would be available only within a Company Managed project.

Otherwise a solution would require a third party app. Are you open to getting an app to address this requirement?

[Md_ Abrarul Huda]

Thanks a lot @Trudy Claspill 

I was able to do it. Not probably the most recommended solution,

I created a separate subtask type for that task only and than assigned a new screen to it. I assigned the screen with the summary field for create and for edit, I removed the summary field.

Working.

[Trudy Claspill]

That is exactly the solution I was considering when I asked about the type of Space with which you were working.

[Olga Cheban _TitanApps_]

hi @Md_ Abrarul Huda !

I can suggest another workaround if you are open to trying out third-party tools.
Here's what you could do:

1) Use a checklist instead of subtasks. In this setup, what was a subtask becomes a checklist item.

You can use our solution Smart Checklist for Jira - it allows you to tag responsible people, add an expandable info section to each step, and track progress with custom statuses. All in all, this makes a checklist a decent alternative for a set of subtasks.

2) Mark the key steps as Mandatory Items. They will be marked with a red asterisk, and you can also configure a validator. It will only allow people move the work item to Done if all mandatory steps are Done.

3) Use the Linked Templates feature. It allows you to prevent users from editing the checklist. They will only be able to change the statuses of checklist items, but not the descriptions or expandable info fields. Also, this feature lets you (as an admin) edit the checklist and push changes to all existing work items that use that template checklist. 

Here's an example of what this can look like:

I hope this helps!
Let me know if you have any questions

[Tinker Fadoua]

@Md_ Abrarul Huda by making the field read only once it is created. 

[Md_ Abrarul Huda]

But I would have to do that for all subtask types, right?
I cannot single-out the one subtask?