nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I restrict User Story description field on any status after "Approved"

Yelena Levitina

Hello,
we have a workflow for User stories, that requires customer approval. In several cases someone managed to change description for a story after it was finalized and approved by customer, resulting in incorrect development logic.

I am able to change properties of a workflow status to restrict editing, but this is being set for all fields except "Comment", restricting me to add story to a sprint or change priorities after it has been approved and locked.

Is there a way to lock description only field after a certain point in a workflow?

Your help will be very much appreciated.

Thank you.

Accepted answers

mfabris

Hi there!

If you have Scriptrunner, you can use behaviours.

You create a new behaviour, and follow the creation step so that it affects your ticket only after "approve" and it locks the description.

All comments

mfabris

Hi there!

If you have Scriptrunner, you can use behaviours.

You create a new behaviour, and follow the creation step so that it affects your ticket only after "approve" and it locks the description.

Yelena Levitina

Thank you very much for your help, I will give it a try.

Yelena Levitina

Hello again,

I installed Script Runner, but do not have "Behaviours" as an option.

Is this a separate product / add-on that I need to find?

I submitted a question to Adaptavists support, but it has been a couple of days and the only reply from them I received is an acknowledgement of my ticket.

Here is what I have:

And this is directions how to get to Behaviours:

What am I missing?

Thank you for your help!

Yelena Levitina

Never mind... Got my answer from support.

Behaviour feature is not available for Jira Cloud, it is only included in Jira Server.

The reason is - the ScriptRunner for Jira Cloud plugin is unable to perform any dynamic validation on issue forms like the server version can with the Behaviors feature due to the restricted functionality and API’s which Atlassian provide inside Jira Cloud because Atlassian only provides a Rest API in Jira Cloud and not the same Java API that the server version contains.

This plug in feature (Behaviours for Jira Cloud) is currently in a gathering interest stage, and they do not have any plans on how this will work or when this will be available.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud