Repository access and data handling

Your code informs the ticket. Your team stays in control.

RefineBrief analyzes code to generate Jira tickets. It does not write or change source code. Your team reviews the proposed tickets before confirming creation in Jira.

Code is context for the ticket.

The connected repositories provide context for the request. RefineBrief does not edit files, create branches, commit, push or open pull requests.

Ticket creation needs your approval.

Review the generated content, code references and open questions. Confirm creation in the linked Jira project when you are ready.

Try the demo without connecting code.

The demonstration uses sample data. Connecting your own Jira environment and repositories is a separate pilot step.

Before a repository connection

Agree how your data will be handled.

These details belong in the pilot agreement, before access is granted.

  1. Access and scope

    Which Jira project and repositories are included? What permissions are required?

  2. Code and AI processing

    Where is code processed, and which AI providers receive content?

  3. Storage and deletion

    What is stored, for how long, and how is access revoked and data deleted?

The website privacy policy covers contact and demo forms. Product data handling is reviewed separately for the pilot.

Read the website privacy policy

Questions about your environment?

Discuss access before connecting.

Use the contact form to share your repository-access and data-handling questions.

Contact RefineBrief