Limitations of Backlog view in Agile Development app

Eriks1
Kilo Contributor

We use Agile Development application on daily basis and there is one thing I am really frustrated about. Why in Backlog view you can only have stories and no other task types?  For example we want to work with defects and I want to have them in Backlog view alongside with user stories.  I tried to use unified Backlog feature and created Triage boards , which allows you to add any task type to the backlog, BUT it anyway creates a user story record and just connects it to parent task ( incident, defect...). and then we need to work on a story record anyway and if comments are added or state is changed parent task is not updated.  IMHO this is huge limitation of ServiceNow.   Before I worked with JIRA a lot, there you could add any task type into the backlog. 

1 ACCEPTED SOLUTION

ettawilson
Mega Sage

Eriks,

There's a long, long history regarding the defect and enhancement tables on the platform. I haven't used those tables for years.

On the story table, there's a field called classification. If you look at the dropdown, the choices are feature and defect. Add enhancement and change the label to story type. 

Etta

View solution in original post

9 REPLIES 9

Eriks1
Kilo Contributor

Forgot to mention, that as workaround we use user story field "Type", where we have - Development , Defect.  For me it seems incorrect to use User Story Type Defect instead of real Defect and user user story record for Generic Task. 

ettawilson
Mega Sage

Eriks,

There's a long, long history regarding the defect and enhancement tables on the platform. I haven't used those tables for years.

On the story table, there's a field called classification. If you look at the dropdown, the choices are feature and defect. Add enhancement and change the label to story type. 

Etta

So, basically you use same workaround as I do.  You user different story types, but not Defects or Enhancements. 

Eriks,

I don't consider it a workaround. Yes, I changed the label but the usage of the field is correct. I've been using stories on the ServiceNow platform for the last 7 years.  

Etta