Describe what you would like us to do:

+1

So, ticket access here means that the person(s) will see any private tickets here. Which could be very sensitive security issues in our infrastructure :sob:

Would it work for them to just make a factory2 project and use that for tracking things? We could file issues we find there and if we have duplicates here just do what we do for any other project: re-file upstream with them.

Failing that, I wonder if we could ask for some pagure RFEs (ok, I know we can ask :)

• a new 'private ticket' permission. 'ticket' then still has everything it has now, except it cannot see or operate on private tickets.
• a way to disable private tickets being set (and we could add a note for some other place to file those or mail them)

Anyhow, lets discuss some more and see what the best way forward is.
To be clear It's not about not trusting these folks, I just want to minimise exposure for us moving forward if we can easily do so.

So, ticket access here means that the person(s) will see any private tickets here. Which could be very sensitive security issues in our infrastructure 😭

Nope, private tickets are only accessible to people who can fix the code: commiters and admins :)

Ah, I must have misunderstood then... sorry about that.

Still it might be more flexable for them to have their own tracker, but I guess thats up to them and what works best for their workflow...

The benefit of using this existing repo is that it's already well know. Having a separate repo for tracking Factory 2.0 services seems to create an unnecessary split.

I think the issue is that we need more information beyond the initial ticket. Are you looking to have tickets assigned to you, to assign tickets to your team-mates, assign tickets to other people? And why do you need this? What other responsibilities will the team be taking on. What other powers will the team need?

I realize these are new documentation requirements, but we have been tasked to better document our workflows, requirements, tasks, and bring a stronger focus to what we are accomplishing. The docs we have on factory2 were last updated in 2016 ( https://fedoraproject.org/wiki/Infrastructure/Factory2/Prehistory ) and 2017 ( https://fedoraproject.org/wiki/Infrastructure/Factory2 )

I'd consider holding on this issue temporarily as we may be moving away from this structure to taiga in the near future.

My understanding is that this is just going to be used to track and coordinate Factory 2 apps deployment nothing else.

For example Factory 2 team wants to deploy a new version of Greenwave, they create a new ticket here and tag it with "Factory 2" tag (this creates a ticket in their Jira tracking system). Once we have the ticket in both tracker we can coordinate on when and how do we want to proceed with this change.

Maybe indeed as @jperrin pointed out we can use taiga for that, but we don't have yet the automation to duplicate taiga ticket to Jira which I think we already have here.

My understanding is that this is just going to be used to track and coordinate Factory 2 apps deployment nothing else.
For example Factory 2 team wants to deploy a new version of Greenwave, they create a new ticket here and tag it with "Factory 2" tag (this creates a ticket in their Jira tracking system). Once we have the ticket in both tracker we can coordinate on when and how do we want to proceed with this change.

That is indeed the intent, for example they have schedule a greenwave update at: https://pagure.io/fedora-infrastructure/issue/7692 but they couldn't add the greenwave tag to it that made the sync to jira happen.
The goal is simply to allow them to do this.

Yeah, i'm ok with that given the private tickets perms.

@pingou you want to go ahead with this? We may be moving trackers at some point, but I'm fine with adding them if you still want to.

@pingou you want to go ahead with this? We may be moving trackers at some point, but I'm fine with adding them if you still want to.

I'll do it (tomorrow), thanks :)

@lucarval @jkaluza @mprahl @gnaponie have been added to this project with tickets access level.

Thanks everyone :)