Atlassian Jira & Confluence Issue tracking system & Wiki

Voluntarily has an Atlassian Open Source License

https://www.atlassian.com/software/views/open-source-license-request

This gives us free access to Atlassian Cloud tools - we are using Jira, Confluence and Bitbucket.

Subscription details here:

https://admin.atlassian.com/s/019b1b85-cc76-4606-b90d-37fce91a7ff0/billing/applications

Access Control

• Site admins and trusted users can invite anyone to any product(s).

• New users with any email domain can join the product(s) enabled on your Product access page, without an invitation or admin approval.

• The products enabled on your Product access page are Jira Service Desk, Jira Software and 2 others.

We operate three Jira Projects:

• Vly-Platform - Software Development VP

• Voluntarily Support - Service desk SUP

• Voluntarily Operations - Process Management VOPS

And a confluence Wiki.

Access to the products is managed through groups

Open

Site-admin group

Grants access to all applications, their administration features and Site administration, which includes managing users and bills

Members - Software Engineering Manager + 1 other for backup. (viv)

Administrators

Grants access to all applications and their administration features (excluding Site administration)

Members - Walter Lim (Design lead)

Membership Process

Access is open to all via self sign up. Notifications for new sign-ups are sent to the site-admin group.

New members are placed in the jira-software-users default access group.

Everyone can submit tickets to the Voluntarily Support helpdesk project but we have to add members to be ticket manager agents.

Admin Process

To be given admin rights you must:

• Be a technical employee of Voluntarily

• or be a trusted and experienced, long term contributor we have met in person.

To allocate a new admin the ‘Software Development Manager’ will find the membership record in Atlassian Management portal and update the permissions.

Revoking Permissions

Access will be revoked for a person:

• No longer meeting the above requirements.

• Not contributing a change to the platform for more than 12 months.

• Any action causing malicious harm to the project/code base.

• Any action breaking the code of conduct towards others.

• Any illegal activity

Auditing Permissions and Changes

https://voluntarily.atlassian.net/wiki/admin/auditlogging.action

Asset Backup and disaster recovery

We are reliant on the Atlassian Cloud software as a service.

We do not run a backup or DR system - too expensive.

Statement from Atlassian:

Per our [Data storage policy|https://confluence.atlassian.com/cloud/data-storage-faq-873871367.html], _Point-in-time backups for your instance are taken every 24 hours for the purpose of disaster recovery. Backups are stored at a location separate from the data center. Use of backup data to roll back changes to application data is not supported. Backups are retained for seven days and then deleted. All backups are encrypted before being taken off-site.

If a critical application failure occurs, our top priority will be to have these applications back up and running in a timely fashion. At this time, we can not guarantee a specific time frame, but we can ensure you that our single most important priority would be to correct any issues keeping the platform down. We will always continue to post to our Atlassian Status page in the event of any error occurs and continue posting updates if needed.

Impact of losing Jira & Confluence

Without Jira, we would lose 1000+ detailed items of work on the system. This would prevent us from making new changes in the short-term and would have a high recovery cost in the reconstitution of the planned work.

Without Confluence, we would lose key documentation for the requirements, design and implementation of the platform as well as operational management pages.

Backup Process

As site-admin go to this page and press ‘Create backup for cloud’.

https://voluntarily.atlassian.net/wiki/plugins/servlet/ondemandbackupmanager/admin

Open

This exports all the Confluence Cloud data in a form suitable for re-install on a new instance of conflence.

once prepared, download the zip file and store offline.

Open Source Project License