STP_SPRINT 0

Issues/bugs

1. Number field is not aligned.

2. On updating the category A and category B such that assignment group mapping is available for
it, the assignment group is still blank.
STP_SPRINT 0

3. Requested for field has 2 different values in the same screen.

4. Once the request is updated and then back arrow is clicked, it relaunches the same
screen without the back arrow.. what is the correct behaviour?

5. User (shinza.srivastava) has created a request for someone else(Sangeetha.kardival),

but in the fulfiller view, requested for is showing the incorrect value, Whereas in the
same screen under request information its displaying the correct value.
STP_SPRINT 0

The same discrepancy even at task level:

STP_SPRINT 0

6. On updating the state in task, the RITM state should be auto-updated.

7. In some cases, task state is appearing as default ‘1’ .

STP_SPRINT 0

8. Assignment group value is not flowing from task to RITM.

STP_SPRINT 0

9. The Approval field should be removed or displayed with the correct value.

10. Assigned to should be auto populated in the task, when the assignment grp is correctly
displayed based on category A and category B and because there is only one person in
that assignment grp.
STP_SPRINT 0

11. Request Information data is NOT AVAILABLE for email created requests. State is None
STP_SPRINT 0

12. The state of the RITM as well as Tasks are having an incorrect entry as state-1.

13. Value of Short description is not flowing from the task to RITM.
STP_SPRINT 0

14. The task do not have any category field.

Queries

1. Should Due date be one of the field while reopening the request form?
2. what all fields can be updated/editable when requestor reopens the request form?
3. what is the difference between - status ,stage and state? should all the three fields be there in
reopening the request form?
4. What all columns should be visible under the catalog task?
STP_SPRINT 0

5. Should Priority by default is LOW?

6. Should Affected CI field be displayed/available?

7. Category B has the same option for all the options in category A, is it ok for now?
8. Suppose we clear category A after selecting category B , shouldn’t category B also auto cleared
as its dependent on category A? ( without saving/submitting the request).

9. Options of the category A are the same even we create the request for a user with a different
location, IS it ok for now?

10. How to differentiate if a ticket is created by an Agent or a normal user?

11. Should category C be visible to user?
12. Is Approval field required in task ?