Feature #6400
closedManually link a commit/revision to a ticket
0%
Description
The issue¶
Actually, a commiter can link a commit to an issue via a special keyword in the commit's comment like :
Fixing a bug (issue #42)
The problem is that developers are lazy (confess it !), and because of the lack of integration between editors/IDE and Redmine (the new REST API may improve this another issue), the special keyword is often forgotten while commiting in the repository, or simply skipped because the developer is too lazy to switch to its browser to look for the issue number.
In the end of the day, I often find myself going to phpMyAdmin directly editing the database (changeset_issues
table) to manually link the ticket to the issue.
- "papercut" issue,
- usability issue,
- bad user experience,
- easy to implement,
- see Ubuntu Paper Cuts
Proposed solution¶
Page "Issue"¶
Design¶
Add a new inline form on top of the page :
Link to revision [ select revision + ] | Update | Watch | Duplicate
The
<select>
box only display the 10 last revisions :
[ Select revision + ]
| Rev 42 |
| Rev 41 |
| Rev 39 |
| Rev 38 |
| Rev 37 |
| Rev 36 |
| [...] |
| More... |
+-------------------+
When I select More..., a javascript prompt pops like below :
+----------------------------------------------------------------+
| Enter the revision or changeset you want to link to this issue |
| |
| [____________________________________________________________] |
| |
| [ OK ] [ Cancel ] |
+----------------------------------------------------------------+
Add a delete link par revision on the associated revision section located on the lower right of the page :
Associated revisions
---
[ Revision 4082 ] | [ Delete link ]
Added by [Jean-Baptiste Barth] [4 days] ago
Fixed broken context_menu on roadmap. [#6351]
---
Scenario : link a revision to an issue¶
- Go to a issue
- Select a revision on the inline form
- A javascript prompt (confirm) pops with the following message :
+--------------------------------------------------+ | You are going to link this issue to revision 42, | | are you sure ? | | | | [ OK ] [ Cancel ] | +--------------------------------------------------+
- Click on OK to confirm the link between issue & revision, or Cancel to abort
Scenario : remove the link between a revision and an issue¶
- Go to an issue #6351
- Click the Delete link link next to Revision 6351
- A javascript prompt (confirm) pops with the following message :
+------------------------------------------------------------------------+ | You are going to delete the link between this issue and revision 6531, | | are you sure ? | | | | [ OK ] [ Cancel ] | +------------------------------------------------------------------------+
Page "Repository > Revision 42"¶
Design¶
Add a new inline form on top of the page :
Link to issue [___________] [ OK ]
Scenario : link a revision to an issue¶
- Go to revision #42
- Fill the text input with the issue ID #6531
- A javascript prompt (confirm) pops with the following message :
+------------------------------------------------------------------------+ | You are going to delete the link between this issue and revision 6531, | | are you sure ? | | | | [ OK ] [ Cancel ] | +------------------------------------------------------------------------+
- Click on OK to confirm the link between issue & revision, or Cancel to abort
Related issues
Updated by Felix Schäfer almost 14 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Please search the tracker before filing an issue, this is already filed and discussed in #2009, thanks for taking the time to file an issue though.
In short: we aware of the problem, but we are currently working on other parts of redmine to make it more robust and maintainable, and are concerned with different data retention issues that are not trivial wrt this issue.