-
Bug
-
Resolution: Done
-
Normal
-
None
-
milestone2
-
False
-
-
False
-
-
-
Moderate
Description of the problem: The MTA 7 workflow only creates one migration wave at a time and uses it for different repos. if a migration wave exists, the workflow will just get the jira ticket associated to it and notify completion but if the repo was updated, it means that no new jira ticket will be created.
How reproducible: 100%
Steps to reproduce:
1. Deploy mta 7
2. Execute the workflow with different repos
3. See how many migration waves are created.
Actual results:
Only one is created.
Expected results: We should have one migration wave per run.
- relates to
-
FLPATH-1549 [MTA 7] Jira ticket is not created when selecting exportToIssueManager=true
-
- Closed
-
- links to