The Ravenshift field guide

Make your tools work
for your team.

Practical guides to planning shifts, understanding tickets, understanding documentation, and keeping useful records. Written by Ravenshift, the Atlassian Marketplace vendor behind the apps.

Workforce management

AI in Jira

Exports & records

Customer insight

Confluence knowledge

Confluence governance

Start with the problem you need to solve

A busy Atlassian team handles several kinds of work at once. Managers need to know who is available. Agents need to understand the latest ticket discussion. Customers and project owners need readable updates and reliable records. These guides separate those questions so you can choose an app and a process with a clear purpose.

For workforce planning, begin with shift scheduling and then review attendance exports. Planned coverage, recorded attendance, and effort logged against a ticket are different records. Keeping them distinct makes staffing decisions and reporting easier to explain.

For AI assistance, begin with the task and the source information. An issue summary can help someone catch up; a chat assistant can help draft follow-up questions; sentiment analysis can highlight a conversation for review. Each output needs a person to check facts, uncertainty, and the intended audience before it becomes a decision or an external update.

For Confluence documentation, use a page overview to find decisions and open questions, and use change comments to record the reasons behind edits. Verify extracted actions against the source page and preserve the timing of historical reasons.

For exports, choose the artifact your recipient needs. A PDF provides a selected, readable snapshot. An attendance spreadsheet supports a reporting question. A project archive aims to preserve a defined body of evidence. Review coverage and limitations rather than assuming every exported file is a complete backup.

Ravenshift publishes these guides as the vendor of the apps discussed. Product links take you to Atlassian Marketplace for current listing details; implementation-specific notes describe the local project reviewed for this edition. Features and availability can change between releases. Validate the installed version on representative data before making it part of your team's routine.

The guides include checklists and illustrative examples you can adapt to a pilot. They do not report invented customer results or promise a particular outcome. If your requirements involve sensitive data, complex retention needs, or a specific deployment, contact us with the workflow you want to evaluate.

Discuss your Jira workflow →