So, a number of our applications/projects have moved from github or fedorahosted to pagure, which is coming along nicely. :)
We do have a number of "projects" on fedorahosted that aren't really software projects, but use fedorahosted almost completely for trac. trac is... not enjoyed by many, so it would be nice to look at what we would need to add to pagure tickets handling in order to cover those cases so we could look at moving some of these 'projects' over to pagure. ;)
So, first many projects use the trac "wiki" for a page with docs on how to file tickets, etc. I think pagure docs already should handle this case very nicely, although perhaps there should be an option to make the 'docs' page the default for a project instead of 'overview' ?
Pagure also has blocking/deps and private tickets.
Now, on to the things I think might be desired:
* Custom ticket statuses (some projects use this to make statuses that are more descriptive for their project, like "upstream" or "accepted" or whatever. This might require splitting the status of tickets to open or closed 'status' and have a seperate 'resolution' or something.
* Tagging of issues. Tons of projects use a 'meeting' keyword to mark tickets they want to discuss in meetings. A way to display only tagged tickets would be good and a bonus would be a irc friendly meeting output to copy and paste. I see a "Tags:" field, but not how to populate it. Is this in progress?
* A way to cc or bcc a group of people on all tickets in a project. Do we already have this?
* Milestones (but I am not sure how much these are used). Some projects have "Fedora 24 Alpha" "Fedora 24 Beta" type milestones for things to be finished before some event. Perhaps we just want to drop this idea in favor of some kind of deadline listing and emiting a message when the deadline is reached? "This ticket was supposed to be done by now!"
* Templates. We use these a lot in infrastructure. Basically when filing a new issue there's a list of templates and when someone selects one it sets the initial contents and assigned and such. These are handy for making sure users give the needed info for a type of request.
* Theres a batch modify plugin that lets you modify a bunch of tickets at once. I don't think this is critical, but might be nice to have.
* Is there a way to completely delete a ticket? Sometimes we have done that on trac for spam tickets.
Thats all I can think of off hand... can other folks think of things we use trac tickets for in the projects that are primarily using trac only?
kevin
On 25 January 2016 at 14:27, Kevin Fenzi kevin@scrye.com wrote:
So, a number of our applications/projects have moved from github or fedorahosted to pagure, which is coming along nicely. :)
.... lots of good things deleted.
- Is there a way to completely delete a ticket? Sometimes we have done that on trac for spam tickets.
That one is going to be important for spam and other reasons "Oh I pasted my password in the form"
Thats all I can think of off hand... can other folks think of things we use trac tickets for in the projects that are primarily using trac only?
That was all I could think of myself.
kevin
infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraprojec...
On Mon, Jan 25, 2016 at 02:27:09PM -0700, Kevin Fenzi wrote:
- Custom ticket statuses (some projects use this to make statuses that are more descriptive for their project, like "upstream" or "accepted" or whatever. This might require splitting the status of tickets to open or closed 'status' and have a seperate 'resolution' or something.
There is a ticket for this: https://pagure.io/pagure/issue/538 but I've been asking what the idea/use-case is for this.
- Tagging of issues. Tons of projects use a 'meeting' keyword to mark tickets they want to discuss in meetings. A way to display only tagged tickets would be good and a bonus would be a irc friendly meeting output to copy and paste. I see a "Tags:" field, but not how to populate it. Is this in progress?
So for each ticket, you can edit the metadata on the right column and add/remove tags there. Then clicking on the tag will give you the list of tickets with this tag. You can also just click on the tag from the tag list shown above all the tickets on the page listing them: https://pagure.io/pagure/issues (right next to [open|close])
- A way to cc or bcc a group of people on all tickets in a project. Do we already have this?
That's not currently there, I do think people @mentioned in a ticket should be added, but it's not there yet. As for batch or CC'ing a group, it'd be a second stage.
I added a ticket to trac the @mention question : https://pagure.io/pagure/issue/690
- Milestones (but I am not sure how much these are used). Some projects have "Fedora 24 Alpha" "Fedora 24 Beta" type milestones for things to be finished before some event. Perhaps we just want to drop this idea in favor of some kind of deadline listing and emiting a message when the deadline is reached? "This ticket was supposed to be done by now!"
So pagure uses tags on ticket for this. You would tag the ticket: easyfix, f24 Then watching the f24 tags you can see a progress bar indicating the percentage of tickets close vs open, for example: https://pagure.io/pagure/issues?tags=0.2 (96 tickets closed, 0 open)
It misses the concept of dead-line, but I always wondered of the applicability of it, what happens when the dead-line is passed? Issue shows in red? Are closed? But then doesn't the devs/users know they are late?
- Templates. We use these a lot in infrastructure. Basically when filing a new issue there's a list of templates and when someone selects one it sets the initial contents and assigned and such. These are handy for making sure users give the needed info for a type of request.
There is a ticket requesting this: https://pagure.io/pagure/issue/585
- Theres a batch modify plugin that lets you modify a bunch of tickets at once. I don't think this is critical, but might be nice to have.
Currently not there, but we have an API and we can extend it as needed.
- Is there a way to completely delete a ticket? Sometimes we have done that on trac for spam tickets.
That's already available
So in summary what is missing is: - cc people to a ticket or at least notify them when @mentioning them - Custom status - Custom templates for issues
Thanks, Pierre
On Tue, 2 Feb 2016 16:19:36 +0100 Pierre-Yves Chibon pingou@pingoured.fr wrote:
On Mon, Jan 25, 2016 at 02:27:09PM -0700, Kevin Fenzi wrote:
- Custom ticket statuses (some projects use this to make statuses
that are more descriptive for their project, like "upstream" or "accepted" or whatever. This might require splitting the status of tickets to open or closed 'status' and have a seperate 'resolution' or something.
There is a ticket for this: https://pagure.io/pagure/issue/538 but I've been asking what the idea/use-case is for this.
yeah, looking at this I think tags could be used for this.
Ie, if you wanted to look at closed tickets that are marked 'upstream' you could use a tag.
- Tagging of issues. Tons of projects use a 'meeting' keyword to
mark tickets they want to discuss in meetings. A way to display only tagged tickets would be good and a bonus would be a irc friendly meeting output to copy and paste. I see a "Tags:" field, but not how to populate it. Is this in progress?
So for each ticket, you can edit the metadata on the right column and add/remove tags there. Then clicking on the tag will give you the list of tickets with this tag. You can also just click on the tag from the tag list shown above all the tickets on the page listing them: https://pagure.io/pagure/issues (right next to [open|close])
Excellent. ;)
- A way to cc or bcc a group of people on all tickets in a project.
Do we already have this?
That's not currently there, I do think people @mentioned in a ticket should be added, but it's not there yet. As for batch or CC'ing a group, it'd be a second stage.
I added a ticket to trac the @mention question : https://pagure.io/pagure/issue/690
ok.
The always cc/bcc thing gets used by a lot of trac's where some group of people always want to get all traffic. For example, I get all infrastructure trac ticket changes and it's very handy to keep track of whats being updated.
- Milestones (but I am not sure how much these are used). Some
projects have "Fedora 24 Alpha" "Fedora 24 Beta" type milestones for things to be finished before some event. Perhaps we just want to drop this idea in favor of some kind of deadline listing and emiting a message when the deadline is reached? "This ticket was supposed to be done by now!"
So pagure uses tags on ticket for this. You would tag the ticket: easyfix, f24 Then watching the f24 tags you can see a progress bar indicating the percentage of tickets close vs open, for example: https://pagure.io/pagure/issues?tags=0.2 (96 tickets closed, 0 open)
It misses the concept of dead-line, but I always wondered of the applicability of it, what happens when the dead-line is passed? Issue shows in red? Are closed? But then doesn't the devs/users know they are late?
Yeah, it would of course vary, and perhaps mean you should remove the f24 tag and add f25.
- Templates. We use these a lot in infrastructure. Basically when filing a new issue there's a list of templates and when someone selects one it sets the initial contents and assigned and such.
These are handy for making sure users give the needed info for a type of request.
There is a ticket requesting this: https://pagure.io/pagure/issue/585
Excellent.
- Theres a batch modify plugin that lets you modify a bunch of
tickets at once. I don't think this is critical, but might be nice to have.
Currently not there, but we have an API and we can extend it as needed.
- Is there a way to completely delete a ticket? Sometimes we have
done that on trac for spam tickets.
That's already available
So in summary what is missing is:
- cc people to a ticket or at least notify them when @mentioning them
- Custom status
- Custom templates for issues
Oh, I just thought of one other thing: rss feeds? For issues, prs, etc?
In fact that could possibly take the place of always cc/bcc (although rss feeds likely wouldn't have the private/sensitive tickets perhaps).
Some of our trac instances use rss to update via zodbot to irc.
kevin
On Wed, Feb 03, 2016 at 04:59:29PM -0700, Kevin Fenzi wrote:
On Tue, 2 Feb 2016 16:19:36 +0100 Pierre-Yves Chibon pingou@pingoured.fr wrote:
That's not currently there, I do think people @mentioned in a ticket should be added, but it's not there yet. As for batch or CC'ing a group, it'd be a second stage.
I added a ticket to trac the @mention question : https://pagure.io/pagure/issue/690
ok.
The always cc/bcc thing gets used by a lot of trac's where some group of people always want to get all traffic. For example, I get all infrastructure trac ticket changes and it's very handy to keep track of whats being updated.
Oh we can easily do that with FMN: Get all the notification about the project `foo` or the projects tagged `bar`. That's even how we do the notifications on #fedora-apps
- Milestones (but I am not sure how much these are used). Some
projects have "Fedora 24 Alpha" "Fedora 24 Beta" type milestones for things to be finished before some event. Perhaps we just want to drop this idea in favor of some kind of deadline listing and emiting a message when the deadline is reached? "This ticket was supposed to be done by now!"
So pagure uses tags on ticket for this. You would tag the ticket: easyfix, f24 Then watching the f24 tags you can see a progress bar indicating the percentage of tickets close vs open, for example: https://pagure.io/pagure/issues?tags=0.2 (96 tickets closed, 0 open)
It misses the concept of dead-line, but I always wondered of the applicability of it, what happens when the dead-line is passed? Issue shows in red? Are closed? But then doesn't the devs/users know they are late?
Yeah, it would of course vary, and perhaps mean you should remove the f24 tag and add f25.
Tags can be edited, ie the f24 tags can be renamed to f25 and plain deleted.
Oh, I just thought of one other thing: rss feeds? For issues, prs, etc?
In fact that could possibly take the place of always cc/bcc (although rss feeds likely wouldn't have the private/sensitive tickets perhaps).
Some of our trac instances use rss to update via zodbot to irc.
Hm, I guess this should be a doable, would the rss feed have only the tickets created or also the comments on tickets?
Pierre
On Thu, 4 Feb 2016 10:57:22 +0100 Pierre-Yves Chibon pingou@pingoured.fr wrote:
On Wed, Feb 03, 2016 at 04:59:29PM -0700, Kevin Fenzi wrote:
On Tue, 2 Feb 2016 16:19:36 +0100 Pierre-Yves Chibon pingou@pingoured.fr wrote:
That's not currently there, I do think people @mentioned in a ticket should be added, but it's not there yet. As for batch or CC'ing a group, it'd be a second stage.
I added a ticket to trac the @mention question : https://pagure.io/pagure/issue/690
ok.
The always cc/bcc thing gets used by a lot of trac's where some group of people always want to get all traffic. For example, I get all infrastructure trac ticket changes and it's very handy to keep track of whats being updated.
Oh we can easily do that with FMN: Get all the notification about the project `foo` or the projects tagged `bar`. That's even how we do the notifications on #fedora-apps
Sure, although how do we handle 'private/sensitive' issues?
...snip...
Oh, I just thought of one other thing: rss feeds? For
issues, prs,
etc?
In fact that could possibly take the place of always cc/bcc (although rss feeds likely wouldn't have the private/sensitive tickets perhaps).
Some of our trac instances use rss to update via zodbot to irc.
Hm, I guess this should be a doable, would the rss feed have only the tickets created or also the comments on tickets?
Seperate feeds I would say... one for ticket status (created, closed, add tag) and one for comments? Or take the bodhi approach and make everything seperate rss feeds. ;)
kevin
On Thu, Feb 04, 2016 at 08:59:32AM -0700, Kevin Fenzi wrote:
On Thu, 4 Feb 2016 10:57:22 +0100 Pierre-Yves Chibon pingou@pingoured.fr wrote:
On Wed, Feb 03, 2016 at 04:59:29PM -0700, Kevin Fenzi wrote:
On Tue, 2 Feb 2016 16:19:36 +0100 Pierre-Yves Chibon pingou@pingoured.fr wrote:
That's not currently there, I do think people @mentioned in a ticket should be added, but it's not there yet. As for batch or CC'ing a group, it'd be a second stage.
I added a ticket to trac the @mention question : https://pagure.io/pagure/issue/690
ok.
The always cc/bcc thing gets used by a lot of trac's where some group of people always want to get all traffic. For example, I get all infrastructure trac ticket changes and it's very handy to keep track of whats being updated.
Oh we can easily do that with FMN: Get all the notification about the project `foo` or the projects tagged `bar`. That's even how we do the notifications on #fedora-apps
Sure, although how do we handle 'private/sensitive' issues?
Project admins get notifications for everything happening in their projects, which I realize now is even better than the FMN approach I described above :)
...snip...
Oh, I just thought of one other thing: rss feeds? For
issues, prs,
etc?
In fact that could possibly take the place of always cc/bcc (although rss feeds likely wouldn't have the private/sensitive tickets perhaps).
Some of our trac instances use rss to update via zodbot to irc.
Hm, I guess this should be a doable, would the rss feed have only the tickets created or also the comments on tickets?
Seperate feeds I would say... one for ticket status (created, closed, add tag) and one for comments? Or take the bodhi approach and make everything seperate rss feeds. ;)
We should make a ticket of this :)
Pierre
On Thu, 4 Feb 2016 17:25:56 +0100 Pierre-Yves Chibon pingou@pingoured.fr wrote:
We should make a ticket of this :)
https://pagure.io/pagure/issue/707
kevin
infrastructure@lists.fedoraproject.org