-
Bug
-
Resolution: Done-Errata
-
Critical
-
MTA 7.0.0
-
None
-
False
-
-
False
-
-
-
No
Description of problem:
Currently, if an application is associated with archetypes, the application is considered reviewed when at least one of its associated archetypes has been reviewed.
An application should be considered reviewed when all associated archetypes have been reviewed. If the behavior is changed, this will also be consistent with when an application is considered assessed. An application is considered assessed when all its associated archetypes have been assessed.
Version-Release number of selected component (if applicable):
MTA 7.0.0
How reproducible:
Always
Steps to Reproduce:
1. Create an application .
2. Create a few archetypes. Associate the application to all the archetypes.
3. Review one of the archetypes.
Actual results:
The application is considered reviewed when at least one of its associated archetypes has been reviewed.
Application 'Review' status shows 'Completed' after one of its associated archetypes is reviewed.
Expected results:
Application should be considered reviewed when all associated archetypes have been reviewed.
Application 'Review' status should show 'In progress' until all associated archetypes have been reviewed and then switch to 'Completed'.
Additional info:
- links to
-
RHBA-2023:120350 Migration Toolkit for Applications bug fix and enhancement update
- mentioned on