Requesting /dev/4 stage for Bahmni team members

[burke (Burke Mamlin)]

@darius

How do we want this to work? Since the Bahmni team is empowered to work on the Concept Attributes feature, should someone from that team be empowered as an Approver and/or Administrator in the TRUNK project in JIRA? If not, is the model that “someone” will notice this at some point and mark the ticket as ready-for-work?

I don’t think we’ve addressed JIRA privs since adopting dev stages. It would seem logical to me that, like GitHub permissions, our permissions in JIRA should be liberal and all /dev/3+ should be able to administer workflows across projects. I’ll start another topic to discuss with infra team about if we are (or could) drive JIRA group memberships (and thereby permissions) automagically from dev stage assignments. Then we’d only have to manually manage exceptional cases.

@darius

For example today TRUNK-4885 was created (by a Bahmni dev) “just-in-time” to send a Pull Request for the Concept Attributes work. But as a newly-created ticket, it was just in “Needs Assessment”.

IMHO, any /dev/3+ at Bahmni should be empowered to perform the assessment to get the ticket into a “Ready for Work” status.

@pascal

Question for infra team: How fine grained are JIRA permissions? Can people have access to assess tickets that are part of a particular epic or milestone?

From what I’ve seen in JIRA, permissions are granted by roles which can be either global or project-specific. I don’t think there’s anything to dynamically change permissions based on issue assignment (there may be a plugin). In any case, I’d rather manage permissions socially rather than technically (i.e., have a liberal permission policy that gives permissions to as many people as possible and use conventions/education to manage expectations).