summaryrefslogtreecommitdiffstats
path: root/src/main/java/com/gitblit/wicket/pages/TicketPage.java
Commit message (Collapse)AuthorAgeFilesLines
* Add dependency to the lucene index, and display reverse dependant tickets ↵Zsombor Gegesy2014-12-091-0/+8
| | | | for pages
* Add 'dependency' to the ticket model and to the ui, with editing possibility ↵Zsombor Gegesy2014-12-081-0/+14
| | | | with a separate relation editor panel
* Gracefully handle missing integration branch in ticket pageJames Moger2014-10-311-4/+10
|
* Tickets - Priority, Severity optionsPaul Martin2014-10-201-0/+6
| | | | | | | | | + Severity indicated via new character indicator and color of ticket icon on ticket list + Priority indicated via new priority icon and color on ticket list + Indexed as integers to provide sorting and maintain language neutral index + Colours and indicator text controlled through CSS classes priority-<x> & severity-<x> + UITicketTest created to generate tickets of all types to ease debugging
* Merge branch 'ticket/197' into developJames Moger2014-09-301-10/+0
|\
| * Fix cropped ticket status indicatorJames Moger2014-09-301-10/+0
| |
* | Merge branch 'ticket/181' into developJames Moger2014-09-171-4/+9
|\|
| * Sanitize ticket text at presentation time to avoid unintended html encodingJames Moger2014-09-171-4/+9
| |
* | Merge branch 'ticket/152' into developJames Moger2014-09-041-6/+9
|\|
| * Fix NPEs when handling referenced milestones that do not existJames Moger2014-09-041-6/+9
| |
* | Extract services manager into a top-level injectable managerJames Moger2014-07-031-1/+1
|/
* Link to open tickets view for open milestones from ticket pageJames Moger2014-06-091-2/+6
|
* Merge branch 'ticket/87' into developJames Moger2014-05-291-1/+1
|\
| * Remove team permission exclusion from Ticket responsible user selectionJames Moger2014-05-291-1/+1
| |
* | Merge branch 'ticket/91' into developJames Moger2014-05-291-3/+11
|\|
| * Support AUTHENTICATED authorization for Ticket responsible selectionsJames Moger2014-05-291-3/+11
| |
* | Correct usage of bugtraq processorJames Moger2014-05-221-3/+3
| |
* | Process bugtraq links in the ticket description and commentsJames Moger2014-05-151-2/+4
| |
* | Refactored common code out of My Tickets and TicketsJames Moger2014-05-011-10/+11
|/
* Do not show patchset details on closed ticketsJames Moger2014-04-151-7/+13
|
* Fix diffstat display for tickets with pending submodule changesJames Moger2014-04-141-1/+1
|
* Improve ticket propose instructions based on primary repository urlJames Moger2014-04-101-13/+14
|
* Fix incorrect ticket branch ref in ticket page changed paths listJames Moger2014-03-161-1/+1
|
* Fix ticket page IOBE when Gitblit is not serving repositoriesJames Moger2014-03-121-3/+9
|
* Clarify ticket fetch instructionsJames Moger2014-03-101-5/+5
|
* Mirrors and read-only repositories must disable review functionJames Moger2014-03-091-1/+1
|
* Allow configuring the default integration branch for a repositoryJames Moger2014-03-081-1/+1
|
* Disable vote & watch links if repository is not accepting ticket updatesJames Moger2014-03-081-2/+2
|
* Fix integration branch in propose instructionsJames Moger2014-03-081-1/+5
|
* Allow selection of integration branch in new ticket pageJames Moger2014-03-081-1/+1
|
* Display an explanation in ticket page if the user can't propose commitsJames Moger2014-03-071-2/+16
|
* Conditionally hide the propose patchset instructionsJames Moger2014-03-071-9/+16
| | | | | | | | There are a few scenarios where a ticket without a patchset should not display propose instructions. 1. the ticket is resolved 2. the repository is configured to reject new patchsets or is read-only 3. the server is configured to reject new patchsets
* DocumentationJames Moger2014-03-061-1/+1
|
* Documentation and clarify git workflowsJames Moger2014-03-061-9/+5
|
* Centralized ticket editing permission controlsJames Moger2014-03-051-2/+1
|
* Delegate closed ticket changes to the Edit Ticket pageJames Moger2014-03-051-136/+147
|
* Allow changing status from edit ticket pageJames Moger2014-03-051-1/+4
|
* Localize the ticket activity tab field name changesJames Moger2014-03-051-1/+5
|
* Externalize some additional stringsJames Moger2014-03-051-1/+1
|
* Prevent <nil> from being stored as a milestoneJames Moger2014-03-051-1/+1
|
* Process bugtraq configuration in markup document renderingJames Moger2014-03-041-1/+1
|
* Ticket tracker with patchset contributionsJames Moger2014-03-031-0/+1527
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A basic issue tracker styled as a hybrid of GitHub and BitBucket issues. You may attach commits to an existing ticket or you can push a single commit to create a *proposal* ticket. Tickets keep track of patchsets (one or more commits) and allow patchset rewriting (rebase, amend, squash) by detecing the non-fast-forward update and assigning a new patchset number to the new commits. Ticket tracker -------------- The ticket tracker stores tickets as an append-only journal of changes. The journals are deserialized and a ticket is built by applying the journal entries. Tickets are indexed using Apache Lucene and all queries and searches are executed against this Lucene index. There is one trade-off to this persistence design: user attributions are non-relational. What does that mean? Each journal entry stores the username of the author. If the username changes in the user service, the journal entry will not reflect that change because the values are hard-coded. Here are a few reasons/justifications for this design choice: 1. commit identifications (author, committer, tagger) are non-relational 2. maintains the KISS principle 3. your favorite text editor can still be your administration tool Persistence Choices ------------------- **FileTicketService**: stores journals on the filesystem **BranchTicketService**: stores journals on an orphan branch **RedisTicketService**: stores journals in a Redis key-value datastore It should be relatively straight-forward to develop other backends (MongoDB, etc) as long as the journal design is preserved. Pushing Commits --------------- Each push to a ticket is identified as a patchset revision. A patchset revision may add commits to the patchset (fast-forward) OR a patchset revision may rewrite history (rebase, squash, rebase+squash, or amend). Patchset authors should not be afraid to polish, revise, and rewrite their code before merging into the proposed branch. Gitblit will create one ref for each patchset. These refs are updated for fast-forward pushes or created for rewrites. They are formatted as `refs/tickets/{shard}/{id}/{patchset}`. The *shard* is the last two digits of the id. If the id < 10, prefix a 0. The *shard* is always two digits long. The shard's purpose is to ensure Gitblit doesn't exceed any filesystem directory limits for file creation. **Creating a Proposal Ticket** You may create a new change proposal ticket just by pushing a **single commit** to `refs/for/{branch}` where branch is the proposed integration branch OR `refs/for/new` or `refs/for/default` which both will use the default repository branch. git push origin HEAD:refs/for/new **Updating a Patchset** The safe way to update an existing patchset is to push to the patchset ref. git push origin HEAD:refs/heads/ticket/{id} This ensures you do not accidentally create a new patchset in the event that the patchset was updated after you last pulled. The not-so-safe way to update an existing patchset is to push using the magic ref. git push origin HEAD:refs/for/{id} This push ref will update an exisitng patchset OR create a new patchset if the update is non-fast-forward. **Rebasing, Squashing, Amending** Gitblit makes rebasing, squashing, and amending patchsets easy. Normally, pushing a non-fast-forward update would require rewind (RW+) repository permissions. Gitblit provides a magic ref which will allow ticket participants to rewrite a ticket patchset as long as the ticket is open. git push origin HEAD:refs/for/{id} Pushing changes to this ref allows the patchset authors to rebase, squash, or amend the patchset commits without requiring client-side use of the *--force* flag on push AND without requiring RW+ permission to the repository. Since each patchset is tracked with a ref it is easy to recover from accidental non-fast-forward updates. Features -------- - Ticket tracker with status changes and responsible assignments - Patchset revision scoring mechanism - Update/Rewrite patchset handling - Close-on-push detection - Server-side Merge button for simple merges - Comments with Markdown syntax support - Rich mail notifications - Voting - Mentions - Watch lists - Querying - Searches - Partial miletones support - Multiple backend options
* Remove incomplete and deprecated TicGit featureJames Moger2013-09-171-86/+0
| | | | Change-Id: Idb7de272589e086da9b2b3a241dcd082c1c8f27b
* Overhauled navigation and flattened lookJames Moger2013-05-191-0/+5
|
* Reorganized to Apache Standard Directory Layout & integrated MoxieJames Moger2013-03-271-0/+81
This is a massive commit which reorganizes the entire project structure (although it is still monolithic), removes the Build classes, and switches to Moxie, a smarter Ant build tookit based on the original Gitblit Build classes. The Ant build script will likely require additional fine-tuning, but this is big step forward.
generated by cgit v1.2.3 (git 2.39.1) at 2025-08-14 00:30:48 +0000