-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After deleting the last application in the status nested table, a blank status is shown #911
Comments
We don't display the section when there are no issues. This is following the same behavior described in (Migration Waves Management([https://github.com/konveyor/enhancements/tree/master/enhancements/migration-waves#migration-waves-management-1] were we don't display the section if there are no issue manager: "This section will only be displayed if there is at least one Issue Manager configured in the Konveyor instance" |
) Resolves https://issues.redhat.com/browse/MTA-877 Resolves #974 #911 - Adds Completed status - Adds In Progress status - Filters out empty status from derived status calculation. This could mean the issue has been deleted from the underlying JIRA instance OR that the Jira ticket is in the process of being created. We have no way of knowing how to interpret empty string, so this filters it out which gives us a more accurate representation of aggregated status. - Add TODO for info text around auth types for JIRA credential creation - Remove Created By field in identity page table - Fixes stale tickets data in migration waves table by mounting the tickets query Signed-off-by: ibolton336 <ibolton@redhat.com>
…nveyor#1124) Resolves https://issues.redhat.com/browse/MTA-877 Resolves konveyor#974 konveyor#911 - Adds Completed status - Adds In Progress status - Filters out empty status from derived status calculation. This could mean the issue has been deleted from the underlying JIRA instance OR that the Jira ticket is in the process of being created. We have no way of knowing how to interpret empty string, so this filters it out which gives us a more accurate representation of aggregated status. - Add TODO for info text around auth types for JIRA credential creation - Remove Created By field in identity page table - Fixes stale tickets data in migration waves table by mounting the tickets query Signed-off-by: ibolton336 <ibolton@redhat.com>
…completed status (#1132) … (#1124) Resolves https://issues.redhat.com/browse/MTA-877 Resolves #974 #911 - Adds Completed status - Adds In Progress status - Filters out empty status from derived status calculation. This could mean the issue has been deleted from the underlying JIRA instance OR that the Jira ticket is in the process of being created. We have no way of knowing how to interpret empty string, so this filters it out which gives us a more accurate representation of aggregated status. - Add TODO for info text around auth types for JIRA credential creation - Remove Created By field in identity page table - Fixes stale tickets data in migration waves table by mounting the tickets query Signed-off-by: ibolton336 <ibolton@redhat.com>
The compound area for aggregated status stays blank if there are no application exported but it shouldn't be clickable.
The text was updated successfully, but these errors were encountered: