-
Bug
-
Resolution: Fixed
-
Low
-
10.109.3
-
Severity 3 - Minor
-
No
Issue Summary
Making rank changes in the backlog in the following views that the context of the Portfolio/Program and PI would be recorded in the Audit Log. "Context" refers to the ID of the Portfolio, Progam or PI.
Steps to Reproduce
Conditions:
1. Epic Backlog - Portfolio
2. Epic Backlog - Portfolio / PI
3. Epic Backlog - Program
4. Epic Backlog Program / PI
The actions are to drag/drop an Epic from one location in the Epic Backlog to another.
Description | Link | Image | Portfolio/Program context shown | PI context shown | Comments |
---|---|---|---|---|---|
Epic Backlog - Portfolio chosen in Tier 1 | Link | N/A | |||
Epic Backlog - Portfolio & PI chosen in Tier 1 | Link | JIRAALIGN-771 Audit Log for ranking is not descriptive, rank type (PI) should be specified | |||
Epic Backlog - Program chosen in Tier 1 | Link | N/A | This bug | ||
Epic Backlog - Program & PI chosen in Tier 1 | Link | refer to above 2 steps. |
Expected Results
1. That the Audit Log entry in a Program context would have the Program ID, like it does for Portfolio.
2. That the PI would have context, such as the ID.
Actual Results
Testing in Portfolio/PI - the audit log has no PI context.
Testing in Program - the audit log has no Program context
Testing in Program / PI - the audit log has no Program context, and no PI context
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JIRAALIGN-771 Audit Log for ranking is not descriptive, rank type (PI) should be specified
- Future Consideration
-
ALIGNSP-14959 Loading...
- mentioned in
-
Page Loading...