As the job system is currently, it looks to me like you can either access them or you can’t. Is that correct?
I’m wondering whether there might be the possibility of allowing access to jobs by roles via filters in the future. IE, if we have a level of staff that does nothing but applications, they would only be able to access jobs marked with ‘app’. Or build staff that could access ‘build’ jobs.
Or does this exist already?
That does not exist currently. Maybe someday but it would be pretty low on the priority list. The jobs system is patterned after the old Pennmush FS3 jobs system, which is far simpler than Anomaly jobs for instance. While some members may wish to filter jobs to only show the types they handle, everyone can see everything.
Got it, thanks for the reply! I’ll put it on the ‘to do when all other things have been done’ back-burner for poking at.
You’re not the only one who’s asked for this, though, so it’s on the wish list. If anyone wants to brainstorm here about how they’d like to see such a hypothetical feature work (e.g. which commands and whatnot) feel free.
Well since you invited… 
The reasoning behind this is basically that on games I’ve run, we often divvy up staffish responsibilities. We may have ‘staff’ that does nothing but applications, or Storytellers who need access to plot requests. In these instances, there may be some stuff that we don’t want some people to see. For example, maybe we want build staff to see build requests, but not plot requests, because they don’t want to be spoiled (or we’re concerned with meta gaming, or something).
So basically what I want is the ability to have certain roles able to only see, create, and comment on jobs in certain filters.
Category-specific permissions: roger.
But beyond that… are there any other commands necessary to allow teams to function better?
So I ran this question by the group of people I have or am running/building games with for ideas.
Along with seeing the jobs in a particular category, do adminish stuff with them, like comment, close, approve applications. The last I think is already covered in the ‘manage_apps’ permission. I personally think it’d be nice if that permission just also automatically included seeing jobs labeled ‘apps’, but others may feel differently.
Allow them to create jobs, but only in their own category. Otherwise request like the other peons.
The ability to auto-assign job categories in the way that the application command does. So that one could do request category=title/description.
Or BETTER, a way to set it up in config so that it does this automatically via aliases. IE, so that I could alias request/build Title=description to job/create Build=title/description.
The second is really ideal, but from what I see of alias-creating, you can’t do spaces. So I don’t know if there’s an easy way to do this, but it’s definitely something I really want.
I’ll post again if anyone comes up with anything else.
Thanks for the suggestions.
What I’m working on right now makes an association between job categories and roles.
A role encompasses many permissions, so you could have an apps_staff role that has manage_jobs, manage_apps, manage_abilities and any other permissions you think they need. Likewise you could have a builder role with a different set of permissions including manage_jobs.
To keep those limited roles from accessing all jobs, you’d limit the APP job category to apps_staff and limit the BUILD job category to builders. (Full admins have access to all jobs.)
Side note - Since permissions are so flexible and job categories can be renamed, I don’t want to have an automatic association between manage_xxx and a job category xxx. It needs to be explicitly set up.
Other roles can still submit jobs into other categories, they just can’t access them via the jobs commands. It would be treated like a request for them.
Not having categories on the request command was actually a conscious choice. I don’t feel that players should have to worry about how staff internally divides up and organizes their work and I didn’t want to make the request command more complicated than it needed to be. A player submits a request, and someone on staff can assign it to the proper category. But if you feel strongly in the other direction, it wouldn’t be hard to add a teeny bit of custom code to the request submit command to let it recognize switches.
I hope that works? Can always refine it more in the future.
Whoa! I can’t believe I missed this - but yes, that sounds amazing! I think it will do what we want, anyway. We’ll see how it shakes out once we’re up and running, but that basic change should make a lot more things possible, thanks!
Here’s a bit more information about the roles and permissions system. One tutorial down! (Actually there are a bunch down but still a bunch to go 
)