apache
[Feature][Config UI] Showing notifications in browser when a blueprint finishes running
Search before asking
- [X] I had searched in the issues and found no similar feature requirement.
Description
It's better to show notifications in browser when a blueprint finishes running since users might not be waiting on the blueprint detail page.
Use case
No response
Related issues
No response
Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.
There was a previously developed Pipeline Indicator Widget that displayed on UI if a running pipeline was detected. This will be restored in order to accommodate this feature.
@mintsweet This is another feature you can work on next, the Pipeline Indicator widget as active on V11 Release, we'll need to restore it on the "Blueprints" Page and "Blueprint Status" Page and potentially other areas of the app where we'd want the user to be aware that there is a running pipeline.
Essentially, if there is a Running pipeline detected (filter all pipelines results), the Pipeline Indicator Widget will be activated so users are aware that there is a running pipeline. See Component src/components/widgets/PipelineIndicator.jsx.
The Widget will likely need updating as the schema of the Pipeline and related Task structure may have changed.
- [ ] Re-Implement
src/components/widgets/PipelineIndicator.jsx - [ ] Apply Styling & UX Updates
@mintsweet This is another feature you can work on next, the Pipeline Indicator widget as active on V11 Release, we'll need to restore it on the "Blueprints" Page and "Blueprint Status" Page and potentially other areas of the app where we'd want the user to be aware that there is a running pipeline.
Essentially, if there is a Running pipeline detected (filter all pipelines results), the Pipeline Indicator Widget will be activated so users are aware that there is a running pipeline. See Component
src/components/widgets/PipelineIndicator.jsx.The Widget will likely need updating as the schema of the Pipeline and related Task structure may have changed.
- [ ] Re-Implement
src/components/widgets/PipelineIndicator.jsx- [ ] Apply Styling & UX Updates
OK, I'll take a closer look at this task later.
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.
This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.