User Story States: how to interpret Funnel?

[atommag]

Hello All, 

Story State has following values: Funnel, Draft, Ready, Work in progress, Ready for testing, Testing, Complete, Cancelled. When creating a user story it is created in the Draft state. 

1) What means Funnel state in this context? Because as default state when creating is Draft I would not expect any state prior to it.  

2) Where can I find a description of these states i.e. how should they be interpreted by users. 

Thank you in advance. Cheers. 

[Miguel Donayre · Accepted solution]

Hello @atommag ,

The "funnel" states come for the SAFe module and it related to that 

• Funnel: Created from Scaled Agile Framework (SAFe) > Epic.

Here is the documentation for it - https://docs.servicenow.com/bundle/madrid-it-business-management/page/product/agile-SAFe/task/create...

I hope that helps!

Mark Correct if this solves your issue and also mark Helpful if you find my response worthy based on the impact.

[atommag]

Hello @Miguel Donayre , 

Thank you for this clarification. For the Epic in SAFe framework it makes sense ... I agree. 

But still the Funnel state is available to be selected and can be saved for the User Story object. 

Is this State field shared across various object i.e. epics / user stories so I will see on the user story level the statuses that might be only applicable for epics?

Thank you. 

[Miguel Donayre]

You are correct it is shared thrugh out the PPM module. You or the admin can make a change to remove it from where you don't need it at. Using a "dictionary Override", that will take it away from the from that want and not affect the rest of the system. Whoever the developer or the Admin of your system should know what that means.

  If this was helpful or correct, please be kind and remember to click appropriately!

[atommag]

Ok ... so I have learned from the implementation team that the Funnel state was introduced to allow for Stories to be in a pre-draft state. In this case the Funnel state prevents that the Stories show up in a Backlog as they are not ready for a backlog yet. So this is actually was customised in our implementation.