Defect - flow, roles, process, documentation?

[Les1]

Agile 2.0 Defect records

Docs

question came to me from a user who is exploring Defects records and OOB process. looking at documentation I could not find the answers.

When a user submits a Defect record for review, then what? where does it go? what roles are needed for changing the State? (it goes to read only after the user Submits to review) 

for example:

user creates a defect record. email notification does go to the agile group assigned (or Assigned To if populated). but member of the assigned agile group is unable to move state of Defect record - what is the intended OOB process supposed to be? I can imagine that Stories can be spawned off the record, but still am confused about what roles are needed for moving the State.

thanks

21 days and no response? i guess nobody else has Defects? 🙂   

i've isolated that role rm_defect_admin is needed to be able to change the defect.state field. but i've not yet isolated what role is needed to see the buttons in the header such as "submit for review" "mark in progress" etc

[Ashish Nahar]

Docs is notmuch of help here and I also searched the OOB process document for Agile 2.0 but again not much of help.

I COuld find from the ACL's which controls write access to the State field.

Please mark helpful or Correct based on my answer

[Les1]

Thanks for researching. In a sub-prod instance when i provide a user either one or all of those roles, the user still can not change the defect.state field (is still read only)

HI told me that it requires "rm_defect_admin" to edit the defect.state field, but like you i didnt see that via the ACL's as it appears that any of the 3 roles you identified would be what is needed. 

[Ashish Nahar · Accepted solution]

Apologies for the late response

I just validated, there was another ACL which is defined.

Allow rm_defect_admin to write to rm_defect.state. Needed as there is an ACL on task.state. Because there is acl on task table. I wouldnt advice making any changes here. were you able to achieve ?

[Les1]

I was able to accomplish with giving user the rm_defect_admin role yes.  i've left feedback to the documentation suggesting they add information around this and around intended OOB flow for defect records.

thank you Ashish