Skip to main content
S
SP_144650764-Participant
4-Participant
April 20, 2026
Solved

Status field remains unset when transitioning to a Requirement

  • April 20, 2026
  • 2 replies
  • 41 views

When changing the item type from Informational to Requirement, the Status field remains unset. Status is not required in an informational type but is required for a requirement type.  It would be better if the item entered into the workflow at the initial state.  Is there a work around to force the item into the initial state, we couldn’t find a way.

Best answer by BKampling_SAI

​@SP_14465076 
The closest workaround I can find involves using a Change Handler.

The limiting factor here is that I couldn’t select the ‘New’ state for the transition target, but I can get it to transition to draft once I created that state transition.
 

 

2 replies

BKampling_SAI
BKampling_SAI13-AquamarineAnswer
13-Aquamarine
May 12, 2026

​@SP_14465076 
The closest workaround I can find involves using a Change Handler.

The limiting factor here is that I couldn’t select the ‘New’ state for the transition target, but I can get it to transition to draft once I created that state transition.
 

 

A
anursinghCommunity Manager
Community Moderator
June 1, 2026

Hi ​@SP_14465076,

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
Of course, if you have more to share on your issue, please pursue the conversation.

Thanks,
Anurag 

Terms & ConditionsAccessibility statement