• Release, region - can use tags.
• Mass closing - probably use the API, write a script?

@ankursinha Curious, how could an anonymous user make a ticket in the old (current) system?

I guess trac just has an option to permit people to open tickets without logging in - https://trac.edgewall.org/wiki/TracPermissions . Try the form out:

https://fedoraproject.org/freemedia/FreeMedia-form.html

It takes you to a "new ticket" page on trac (via a GET request?), like this one, for example:

https://fedorahosted.org/freemedia/newticket?reporter=ankursinha@fedoraproject.org&summary=%20Ankur%20Sinha%20from%20UNITED%20KINGDOM%20wants%20a%20Workstation%20Product%2064Bit.&description=Ankur%20Sinha,[[BR]]Something%20%20[[BR]]In%20fedora%20%20[[BR]]Awesome%20[[BR]]UNITED%20KINGDOM.[[BR]]%20&version=Workstation%20Product%2064Bit&keywords=APAC,%20Fedora%2024,%20September%202016&email=ankursinha@fedoraproject.org&country=UNITED%20KINGDOM

We have a few weeks to go only. :timer:

@twohot , @pingou , @kevin - any suggestions/ideas on this migration?

(Should I file the ticket on the infra repo, or is it OK here?)

Using the API and a API token you could easily have the php script open tickets on pagure. All the tickets would appear as being opened by the person whom API token it is, but worst case we could make a specific account for that.

Mass-closing isn't available in the API, we could consider adding it. The easiest for the moment would be to iterate over all the tickets to close and do them one by one.

@pingou - I'll start tinkering with the API. We intent to use the API to extract metrics about the requests already. I may need some help with the web part - not my strong suit :)

Here's what I'm thinking:

• A Free-Media group
• A Free-Media/Tickets repository - this is where the tickets will be opened (tickets will be private). All members of the Free-Media group will have write access to this, so that they can accept + close tickets.
• A Free-Media/Housekeeping repository where we keep the scripts. Again, all members of the Free-Media group will have write access to this.

As for the API token it'll be needed for:

• opening new tickets (people from outside the community will do this via our interface)
• mass closing tickets
• managing duplicates and the sort

I guess it's OK if everyone from the Free-Media group has their own token - we can write some scripts to enable them to manage tickets via the command line. I don't reckon this will be an issue?

As for syncing the FAS group and the pagure group, how would one do that? That's quite important for membership management. Do groups have "admins" and "users" - I don't think so?

I've started setting it up. Here's a test ticket: https://pagure.io/Free-Media/Tickets/issue/1 - does this look OK?

(Any chance tickets can be sorted using the custom fields that have been set up?

I see that projects can have different access levels (https://pagure.io/pagure/pull-request/1177):

• admin
• tickets
• commit

Somehow I can't find these in the settings. Can you please help? Then, we can simply give the Free-media pagure group "tickets" access, and the few admins can own the repos.

PS: Can we mention groups (hello @Free-Media!)

@ankursinha That pull-request hasn't been merged to master yet :) There is currently #1796 which we are working on getting into master.

Tickets can be filtered using the custom keys but this has to be done via the URL for the moment using ?ckeys=<key>&cvalue=<value>

For the example ticket you're linking to above, I can't quite see it since it is private :)

For pagure group <-> FAS group sync we are working on a script to automate that: https://pagure.io/fedora-infrastructure/issue/5740

I guess it's OK if everyone from the Free-Media group has their own token - we can write some scripts to enable them to manage tickets via the command line. I don't reckon this will be an issue?

I am not quite sure to understand what you mean here.

Btw, there is https://stg.pagure.io if you want to play around (rather than using the production instance)

@ankursinha That pull-request hasn't been merged to master yet :) There is currently #1796 which we are working on getting into master.

Ah, no worries. For the time being, the entire group can have write acess.

Tickets can be filtered using the custom keys but this has to be done via the URL for the moment using ?ckeys=&cvalue=

Ah! Awesome! I'll just make a note on the project README page. That should be OK.

For the example ticket you're linking to above, I can't quite see it since it is private :)

EEE - I'll do it all on pagure and leave it open there so that everyone can help :)

For pagure group <-> FAS group sync we are working on a script to automate that: https://pagure.io/fedora-infrastructure/issue/5740

Awesome. Keeping an eye on it (and maybe helping a bit too!)

I guess it's OK if everyone from the Free-Media group has their own token - we can write some scripts to enable them to manage tickets via the command line. I don't reckon this will be an issue?

I am not quite sure to understand what you mean here.

This is just to do with the permissions we provide. If the entire group has write access, then they can all use their own tokens to make changes to the repo. I don't think this is an issue at the moment.

Btw, there is https://stg.pagure.io if you want to play around (rather than using the production instance)

Duh! Of course there is! I'll move my tinkering to staging. :)

Ah! Awesome! I'll just make a note on the project README page. That should be OK.

You can save the filtering using the report feature, check the bottom of the page.

Ah! Awesome! I'll just make a note on the project README page. That should be OK.

You can save the filtering using the report feature, check the bottom of the page.

Works like a charm: https://stg.pagure.io/Free-Media/Tickets/issues?ckeys=Country&cvalue=United%20Kingdom :)

Or https://stg.pagure.io/Free-Media/Tickets/report/UK%20Requests :) but I saw you already found that :)

Yea :)

I'm still thinking we'll end up with quite a few reports and the list will get rather long:

• one for closed tickets for each country
• one for open tickets for each country

Maybe on the front page, I could add all the links to the README instead?

The alternative is to use tags instead of custom fields for countries - do you think that would work better?

BTW, think I found a bug - when a project is under a namespace, the search box on the issues page doesn't take the namespace into account and gives a 404 as a result. Checking to see if it's already been filed now.

Yes that bug on the search feature has been reported, it's been annoying :(

Yes that bug on the search feature has been reported, it's been annoying :(

If it's known, it'll get fixed :)

I've hacked up a script that generates a list of report links like this:
https://stg.pagure.io/Free-Media/Tickets . I'll just generate more links to reports in the meantime.

How would one use multiple keys (like Country and Year) in a report, by the way? I tried a few changes to the URL, but it didn't quite work.

This is the form at the moment - https://robert.fedorapeople.org/freemedia/FreeMedia-form.html

We may use different pagure repos to hold tickets for different regions, just to make it easier to manage, and we're also looking at making the form available in different languages:

https://pagure.io/Free-Media/Housekeeping/issue/9
https://pagure.io/Free-Media/Housekeeping/issue/10
https://pagure.io/Free-Media/Housekeeping/issue/11

There's so much work that I'm beginning to panic! :joy_cat:

The last update was 5 years ago, no further requests, updates or actionable tasks since then, I'm going to close this issue for now to reduce our backlog.