Ticket system #1
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: meta/mintee#1
Reference in New Issue
Block a user
In conversation with @soup we have discussed a ticket system that combines PRs, issues, and possibly other ticket types into the same basic type of representation. This would allow issues to become PRs and vice versa.
There should be a milestone ticket that is a summary of the tickets that are its dependencies (of any kind).
Some ticket types discussed thus far:
Each of these ticket types has the capability to become another ticket type.
Having had time to think this idea through, I think the best idea would be to not really differentiate between ticket types and rather just have tickets and be able to add and remove attributes from and to them.
Tickets should be able to have dependencies and should all be mirrored to e-mail as threads and activitypub as posts.
Do we want to have some sort of analog to gitea/forgejo's projects?
They are useful, but have the downside of storing what is often the same information in two places at once.
I like the idea of the equivalent to projects just being groups of tickets.
I was thinking that the utility of projects might be replaced with one ticket with many dependencies. Is that what you mean?
I was thinking like a separate type of thing called a project which simply groups tickets but that works the same way, I think.