I’m attempting to assign the following topic to Marius Schwarz as
mschwarz
but it will not accept it
https://discussion.fedoraproject.org/t/fedora-linux-becomes-aware/183135
I can search Discourse and it readily displays Marius’ name.
I’ve done this with two other names on different topics and they worked.
Any assistance appreciated.
Thanks
So far, from my experimentation, the only names that I can assign to seem to be folks related to the fedora project (very limited testing). Is it possible there is a group limitation for assignment? Can this be lifted to allow anyone with a FAS login to be assigned to?
The only thing different I see about @mschwarz is that they haven’t logged in here is 4+ years… so perhaps it’s put them in an inactive state of some kind?
I don’t see anything obvious on the profile. Perhaps ask them to login again and see if it starts working? Failing that would need to look more…
I’ll contact him. Thanks again, Kevin.
@kevin I reached Marus Schwarz and he successfully logged back it. However, that did not change the fact that I can’t assign the topic to him.
@glb investigated the documentation we are wondering how “Assign” is currently set. “Everyone” seems to imply any one can assign topics but what if that was TL0 ? (of course I have no idea what my level is or that even matters).
Flying by the seat or my pants here but assignment would help us in managing the Fedora Magazine workflow.
You are Forum Level 3, if you click on your avatar in the above post you can see it (or in your profile).
What are the pages where you previously, successfully assigned users?
It was originally a test ticket which was deleted, but I’ve recreated one. This was created by me then assigned to GLB.
https://discussion.fedoraproject.org/t/test-topic-for-assignemt-issue/183572/2
However, when I try to assign this one to mschwarz (Marius Schwarz) It doe not work.
https://discussion.fedoraproject.org/t/fedora-linux-becomes-aware/183135/4
If we compare glb’s account
with
mschwartz account
we can see that glb is in a number of sigs including magazine editors and magazine.
So I would conclude that one must be in one of those sigs to be assigned a project in ‘magazine workflow’
You can test by assigning to me if you want - I’m in some sigs but not in magazine.
MatH (sigh) doesn’t work trying to assign to you. This is unfortunate. So there doesn’t appear to be a way to assign to just anyone. They have to be in a sig ?
What we are looking for is a way to insure that we can track who will be responsible for the article the topic represents in the Fedora Magazine and we communicate, via comments on the topic, with that person.
@glb I guess we can edit the topic to add that person’s “handle” and we can address them directly but that’s another step in the process to forget.
Thank you MatH. If you have any ideas they would be appreciated.
I would then surmise that the way that the ‘team workflows’ ‘fedora magazine’ category is set up contains somewhere the list of FAS groups that have access to said category.
Perhaps an admin can make that category literally ‘everyone’ or perhaps ‘fedora contributors’ which is anyone that is in any SIG.
We are having a similar problem in the new Forge, where in Join SIG, we want to add literally anyone new to a ticket issue, but we can’t assign people outside of our SIG. (So I can’t recommend tracking these magazine articles on the Forge yet either).
A FAS account is required to log into the Discussion and that is where we want folks to start the workflow. It is also necessary to access the WordPress (WPEngine) site where the articles for the Magazine are writtenl
So ‘fedora contributors’ sounds like the SIG we need.
Do you know who the admin might be? @glb do you know and does this sound like a reasonable path?
https://discussion.fedoraproject.org/g/admins
Seeing that Justin is on that list, and that he has previous experience with the Fedora Magazine workflow, it seems like he would be the best candidate to contact for help with this specific problem.
I know very little about how DIscourse permissions, sigs, trust levels, etc. work and even less about this specific plugin. I could set up a local test instance of Discourse to experiment with, but it will take me some time to get that set up.
To be in ‘fedora contributors’ one must be in any other SIG.
mschwartz for example is not in any SIG, so is not in ‘fedora contributors’.
So what you want is ‘anyone with a FAS account’.
Don’t do that, just get an admin to check the team workflows and fedora magazine category.
@jflory7 Is it possible to set up a SIG that covers ‘anyone with a FAS account’ and then set the Assign setting in Discourse so that we can move topics between folks in that SIG ?
This would allow the FM editors to create topics and assign them to FAS members as well as reassign them if someone assumes responsibility for an article (hence topic).
I confess to not being the most Discourse-savvy person on the admin list.
@moderators, @admins, @trust_level_4, @trust_level_3, anyone know more or how to help @rlengland with this request?
I certainly do not know any more about how Discourse works. However, I found the following screenshot here which, I think, illustrates the problem.
In the description for the “assign allowed on groups” setting, it appears to imply that the settings for “who can assign topics” and “to whom topics can be assigned” are one and the same setting. At least, that is my reading of it.
Our problem is that we want to be able to assign topics to anyone, even newcomers. We don’t really want to grant everyone the ability to assign topics to others, but it seems that we cannot have the one without the other?
I have only roughly skimmed this topic, but some of the recent requests seem to be based only on speculations about what the origin is.
The first thing I see on this user account is that he is only TL1, so still a type of “entry level”: had something be assigned before to a TL1? (might be worth testing, there should be sufficient TL1 and TL2 around 
)
With Gregory’s last post in mind, I could imagine the issue is as simple as that only TL2 (which is the actual “I have arrived” level) and above can be assigned. Based on the ideas of the different trust levels, I could imagine TL2 is the default of the system.
If that is a setting, and if it shall be allowed that you can assign also to TL1 (I suggest to not use TL0 tbh), a site-admin should be able to change it. But I would test before changing settings (and maybe at some point start to document when we modify settings).
I don’t have experience with how the workflow of magazine is setup, so I can also only speculate. But I don’t think this one setting about TL is the only condition for assigning, but only one condition of multiple conditions that have to be met. I don’t think at the moment every TL2/TL3 can do assignments in your workflow, can they?
I have to be careful as I do not know what the actual original idea of this function is, but to enforce always that the person assigning and the person assigned are of the same min-TL doesn’t sound reasonable. That’s why I assume this to be only one condition.
