| | |
|---|
| | | ## Setting up Tickets |
|---|
| | | |
|---|
| | | *PREVIEW 1.4.0* |
|---|
| | | *SINCE 1.4.0* |
|---|
| | | |
|---|
| | | By default, Gitblit is not configured for Tickets. There are several reasons for this, but the most important one is that you must choose the persistence backend that works best for you. |
|---|
| | | |
|---|
| | |
|---|
| | | |
|---|
| | | tickets.service = com.gitblit.tickets.BranchTicketService |
|---|
| | | |
|---|
| | | Your ticket journals are persisted to `id/{shard}/{id}/journal.json`. These journals are stored on an orphan branch, `refs/gitblit/tickets`, within your repository. This allows you to easily clone your entire ticket history to client working copies or to mirrors. |
|---|
| | | Your ticket journals are persisted to `id/{shard}/{id}/journal.json`. These journals are stored on an orphan branch, `refs/meta/gitblit/tickets`, within your repository. This allows you to easily clone your entire ticket history to client working copies or to mirrors. |
|---|
| | | |
|---|
| | | #### Redis Ticket Service |
|---|
| | | |
|---|
