---
# System prepended metadata

title: Jira Stuff

---

# Jira Stuff

## Figure out who sees what

Our projects & permissions

 BCN - p/e (they manage) ; closeknit (they manage)
CBSM - edenhealth (limited); closeknit (all); p/e (limited discretionary)
 CPB - closeknit (all); p/e (limited discretionary)
 future state of project unknown/might be defunct
 criteria for defunct - needs signoff from Jess Vanvas

## follow-up actions

export user list - matt review edenhealth group BCN project
review CBSM access


## Migration of BCN from p/e to our instance

- own project

access granularity
CBSM - who should have access?

## old notes
- Linking CBSM tickets to productive edge BCN tickets
- Productive edge users can enroll automatically
  - What do we want them to see?
    (Currently, they can sign in but no visibility)
- Review existing roles and permissions
  - This comes from a permissions scheme shared across projects
  - Should there be any changes or exceptions?
  - We don’t want to make changes to the Jira site-level scheme itself
    (Unless we’re looking to make a site-wide change)
    We add/remove roles from people or groups instead on a project level
Roles are editor, user, auditor
Note that creating team-managed projects is disabled
Harder to audit
We’re going to have data-loss prevention plugins running that need to scan for PHI. Permissions need to allow for audit
Explain difference between site-level groups and project-level roles
Have someone share their screen as I walk them through adding a user
What to expect from me, a site admin
Site-level changes, plugins, billing, etc.
What to expect from Project Managers
Project-level administration
If there’s something you can’t do, don’t hesitate to reach out to me or anyone with site-admin access (with the right comes responsibility)
Q&A
