Feature #16854

collective sysadmin redmine user

Added by groente 2019-07-05 13:09:04 . Updated 2019-08-05 13:22:54 .

Status:
Resolved
Priority:
Normal
Assignee:
intrigeri
Category:
Infrastructure
Target version:
Start date:
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

we’d like to have a possibility of assigning tickets to the sysadmin team in general.
for this we’d need to:

- create a role user for our team on Redmine
- communicate about it to -summit@ (and in our doc?)
- update or deprecate https://redmine.tails.boum.org/code/projects/tails/issues?query_id=262 and https://redmine.tails.boum.org/code/projects/tails/issues?query_id=267


Subtasks


History

#1 Updated by CyrilBrulebois 2019-07-10 10:34:16

  • Target version changed from Tails_3.15 to Tails_3.16

#2 Updated by groente 2019-07-29 12:09:24

  • Status changed from Confirmed to Needs Validation
  • Assignee changed from groente to Sysadmins

There’s now a group Sysadmins to which tickets can be assigned, shall I make a shout out to the world to start using this for requesting sysadmin work instead of making individual assignments?

#3 Updated by intrigeri 2019-07-31 15:55:09

> There’s now a group Sysadmins to which tickets can be assigned,

Woohoo!

> shall I make a shout out to the world to start using this for requesting sysadmin work instead of making individual assignments?

Yes, please :) This matches what we decided: “communicate about it to -summit@ (and in our doc?)”.

And then we’ll have to figure out how we can use this new tool to track our collective plans / to do. So far we had:

Thoughts?

#4 Updated by groente 2019-07-31 16:50:41

  • Status changed from Needs Validation to In Progress
  • % Done changed from 0 to 50

intrigeri wrote:
> Yes, please :) This matches what we decided: “communicate about it to -summit@ (and in our doc?)”.

A shout out to -summit has been sent. I’m unsure where this could be documented in our git repo’s. Or did you mean the documentation on our public website?

> And then we’ll have to figure out how we can use this new tool to track our collective plans / to do. So far we had:
>
> * https://redmine.tails.boum.org/code/projects/tails/issues?query_id=262 (sysadmin shifts) → do we want to now assign all this kind of work to the “Sysadmins” group, and then adjust the custom query to filter on the assignee? The drawback is that as soon as we assign such a ticket to an individual, it appears in no collective view anymore. So I’m not sure what to do. I suspect we should keep this existing view as-is and create a new one for tickets assigned to Sysadmins.

I’m in favor of keeping this view as-is. Personally, I have no interest in another view for tickets assigned to Sysadmins, as they already appear on my personal page anyway.

> * https://redmine.tails.boum.org/code/projects/tails/issues?query_id=267 (other work) → I don’t know if/how this relates to the new Sysadmins group.

I suppose atleast the tickets with no current assignee should be assigned to the group. Apart from that, I see little further relation.

#5 Updated by groente 2019-08-01 09:37:53

  • Status changed from In Progress to Needs Validation
  • % Done changed from 50 to 60

groente wrote:
> intrigeri wrote:
> > * https://redmine.tails.boum.org/code/projects/tails/issues?query_id=267 (other work) → I don’t know if/how this relates to the new Sysadmins group.
>
> I suppose atleast the tickets with no current assignee should be assigned to the group. Apart from that, I see little further relation.

That’s done now. Anything left to discuss here or shall we close the ticket?

#6 Updated by intrigeri 2019-08-03 17:51:51

> intrigeri wrote:
>> Yes, please :) This matches what we decided: “communicate about it to -summit@ (and in our doc?)”.

> A shout out to -summit has been sent.

\o/

> I’m unsure where this could be documented in our git repo’s. Or did you mean the documentation on our public website?

I don’t remember what we meant when we decided “and in our doc?” during our last meeting. This being said:

>> And then we’ll have to figure out how we can use this new tool to track our collective plans / to do. So far we had:
>>
>> * https://redmine.tails.boum.org/code/projects/tails/issues?query_id=262 (sysadmin shifts) → do we want to now assign all this kind of work to the “Sysadmins” group, and then adjust the custom query to filter on the assignee? The drawback is that as soon as we assign such a ticket to an individual, it appears in no collective view anymore. So I’m not sure what to do. I suspect we should keep this existing view as-is and create a new one for tickets assigned to Sysadmins.

> I’m in favor of keeping this view as-is. Personally, I have no interest in another view for tickets assigned to Sysadmins, as they already appear on my personal page anyway.

OK. So to make that view keep working, we keep adding stuff to that view via a “Blocks” relationship, right?

>> * https://redmine.tails.boum.org/code/projects/tails/issues?query_id=267 (other work) → I don’t know if/how this relates to the new Sysadmins group.

> I suppose atleast the tickets with no current assignee should be assigned to the group. Apart from that, I see little further relation.

OK!

#7 Updated by groente 2019-08-05 11:16:08

intrigeri wrote:
> > intrigeri wrote:
> > I’m unsure where this could be documented in our git repo’s. Or did you mean the documentation on our public website?
>
> I don’t remember what we meant when we decided “and in our doc?” during our last meeting. This being said:
>
> * I see little value in documenting this only in our own repo.

Agreed.

> * Documenting it on https://tails.boum.org/contribute/working_together/roles/sysadmins/ might help contributors who are not on -summit (yet).

That does seem like the most sensible spot to document this. Do you feel like updating the text there?

> >> And then we’ll have to figure out how we can use this new tool to track our collective plans / to do. So far we had:
> >>
> >> * https://redmine.tails.boum.org/code/projects/tails/issues?query_id=262 (sysadmin shifts) → do we want to now assign all this kind of work to the “Sysadmins” group, and then adjust the custom query to filter on the assignee? The drawback is that as soon as we assign such a ticket to an individual, it appears in no collective view anymore. So I’m not sure what to do. I suspect we should keep this existing view as-is and create a new one for tickets assigned to Sysadmins.
>
> > I’m in favor of keeping this view as-is. Personally, I have no interest in another view for tickets assigned to Sysadmins, as they already appear on my personal page anyway.
>
> OK. So to make that view keep working, we keep adding stuff to that view via a “Blocks” relationship, right?

Correct!

#8 Updated by intrigeri 2019-08-05 11:18:22

  • Status changed from Needs Validation to In Progress
  • Assignee changed from Sysadmins to intrigeri

>> * Documenting it on https://tails.boum.org/contribute/working_together/roles/sysadmins/ might help contributors who are not on -summit (yet).

> That does seem like the most sensible spot to document this. Do you feel like updating the text there?

I will!

#9 Updated by intrigeri 2019-08-05 13:22:54

  • Status changed from In Progress to Resolved
  • % Done changed from 60 to 100

Applied in changeset commit:tails|765210391edae4c590ffed9b6c0c9669fdf0358f.