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: 

Need to Prevent the Ability to add commitment (sub-task) to an Epic that has an existing Commitment

Saravanan Ravikumar
June 3, 2019

Hi,

Scenario -

When there is a Issue type called epic and the sub-task called Commitment

Given there is an Epic with a 'Commitment' in "Committed" or "Met" status
When I want to add another 'Commitment' (sub-task) to the Epic
Then I should NOT be permitted to do so

Given there is an Epic with a 'Commitment' in "Not Met" or "Withdrawnt" status
When I want to add another 'Commitment' to the Epic
Then I should be permitted to do so

I tried to achieve it using behavior but failed.

 

How to handle this? please guide me on this

Regards

1 comment

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

Saravanan Ravikumar
June 4, 2019

Can anyone help on this.

TAGS
AUG Leaders

Atlassian Community Events