Today we have "Report issue" which links to GitHub, we also have scattered around the concept of reporting issues.
We should formalize reporting an issue as a feature in Studio at the root level as a Command.
Admin should expose a Grain interface for issues that we can call. The Admin implementation would produce events from this.
We want to instead of requiring people to have a GitHub account be able to report the issues they see.
In Admin we should then be able to create an issue on GitHub from the issue, but we can also have a conversation to ask for more details.
The issue should have different statuses:
- Reported
- In triage
- Not approved
- Approved
- Closed
When it is converted into a GitHub issue - the status should be changed to "Approved". When an issue is opened, it goes into "In triage". When setting "Not approved" on an issue, the UI will need to pop up a dialog requiring input as to why we won't work on it.
When we convert an issue to GitHub, we need to keep track of the GitHub issue number.
We need to register a GitHub WebHook for tracking issues that will get changes done to issues on the Cratis/StudioIssues repository. Updates to the issue should be reflected back. And
Today we have "Report issue" which links to GitHub, we also have scattered around the concept of reporting issues.
We should formalize reporting an issue as a feature in Studio at the root level as a Command.
Admin should expose a Grain interface for issues that we can call. The Admin implementation would produce events from this.
We want to instead of requiring people to have a GitHub account be able to report the issues they see.
In Admin we should then be able to create an issue on GitHub from the issue, but we can also have a conversation to ask for more details.
The issue should have different statuses:
When it is converted into a GitHub issue - the status should be changed to "Approved". When an issue is opened, it goes into "In triage". When setting "Not approved" on an issue, the UI will need to pop up a dialog requiring input as to why we won't work on it.
When we convert an issue to GitHub, we need to keep track of the GitHub issue number.
We need to register a GitHub WebHook for tracking issues that will get changes done to issues on the Cratis/StudioIssues repository. Updates to the issue should be reflected back. And