meta/mintee
5
0
Fork 0
Code Issues 7 Pull Requests Projects Releases Activity

Ticket system #1

New Issue
Open
opened 2024-01-30 16:56:27 -07:00 by emma · 7 comments
emma commented 2024-01-30 16:56:27 -07:00
Owner
Copy Link

In conversation with @mars 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.

In conversation with @mars 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.
emma added the
enhancement
 label 2024-01-30 16:56:27 -07:00
emma commented 2024-01-31 14:10:05 -07:00
Author
Owner
Copy Link

There should be a milestone ticket that is a summary of the tickets that are its dependencies (of any kind).

There should be a milestone ticket that is a summary of the tickets that are its dependencies (of any kind).
emma commented 2024-01-31 14:11:17 -07:00
Author
Owner
Copy Link

Some ticket types discussed thus far:

  • Issue
  • Pull Request
  • Discussion/Thread
  • Milestone
  • Feature

Each of these ticket types has the capability to become another ticket type.

Some ticket types discussed thus far: - Issue - Pull Request - Discussion/Thread - Milestone - Feature Each of these ticket types has the capability to become another ticket type.
emma commented 2024-07-02 08:45:34 -06:00
Author
Owner
Copy Link

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.

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.
sashakoshka commented 2024-07-02 19:32:49 -06:00
Owner
Copy Link

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.

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.
emma commented 2024-07-02 22:15:19 -06:00
Author
Owner
Copy Link

I like the idea of the equivalent to projects just being groups of tickets.

I like the idea of the equivalent to projects just being groups of tickets.
sashakoshka commented 2024-07-03 00:40:32 -06:00
Owner
Copy Link

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?

> 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?
emma commented 2024-07-03 15:37:26 -06:00
Author
Owner
Copy Link

I was thinking like a separate type of thing called a project which simply groups tickets but that works the same way, I think.

I was thinking like a separate type of thing called a project which simply groups tickets but that works the same way, I think.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: meta/mintee#1
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?