The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Using of the field " original story point" for jira

Igor Bangue
March 6, 2025

Hello

I want to do some modification of the " Original story point " field for jira but I have any question :

1°) I want to lock the " original story point" field so that it is no longer be edited once it has been filled in. it should only be visible in read-only mode, in order to keep the initial estimate.

 

2°) when the user story is duplicated or cloned, that duplication of user story should not duplicate the value of that original story point field.

 

Can you help me please ?

Best regard !

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Felipe Perez _ServiceRocket_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 6, 2025

Hi Igor!

Good day to you! I'm Felipe from the ServiceRocket team.

Regarding your questions, please find the answer below:

Lock the "Original Story Point" Field After It’s Filled In

To prevent users from modifying the Original Story Point field once it has been set, you can use Workflow Properties to make it read-only.

  1. Navigate to Administration > Issues > Workflows.
  2. Edit the workflow used for your issues.
  3. Add the following workflow property to the View/Edit screen of the issue in statuses where the field should be locked:
    1. Key: jira.issue.editable
    2. Value: false
  4. Save and publish the workflow.

The field will become uneditable once the issue reaches the specified status.

Prevent the Field from Being Copied When Cloning an Issue

By default, Jira clones all issue fields, including Original Story Point. You can prevent this by using a Workflow Post Function.

  1. Navigate to Administration > Issues > Workflows.
  2. Edit the Create Issue transition in your workflow.
  3. Add a Post Function:
    • Select “Update Issue Field”.
    • Set Original Story Point to empty (null).
    • Condition: Apply only if the issue is cloned.
  4. Save and publish the workflow.

When a cloned issue is created, the Original Story Point field will be automatically removed.

Best Regards,
Felipe

DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events