View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0020605 | mantisbt | custom fields | public | 2016-02-15 05:55 | 2016-09-02 09:28 |
Reporter | mantisiator | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Summary | 0020605: Secondary Key Issue counter automatically filled per "stable" project | ||||
Description | Hi, Please let me come back to the Issue 10920 stating : The issue number is global to all projects defined in a Mantis instance, but I would like to have a field which is dependent of the project in order to log "the issue order in this project". Additional Information Project 1 - issue 001 - order 001 This issue has raised a comment stating that the secondary key would not be "significant" in case one issue is moved from a Project to another, which I can understand. What do you think ? Thank you very much in advance ! | ||||
Tags | No tags attached. | ||||
This is a very specific request. Currently a feasible way to achieve that is create a custom plugin that maintains that numbering, making use of events:
Moving between projects is still an issue, but could be solved by:
|
|
Thanks a lot for your comment. For additional information, this feature can also be used when moving from an Issue Tracking system to another system. In fact , in that case, the secondary key could be used to keep track of the former system numbering (in my case, the former system allows a numbering per project. Thereofore, having that feature could allow an easy migration) |
|
Hi @cproensa, 0005715: Issue ID for each project Indeed, the counter feature could be a generic -native- feature "per project" in case we use (which is also my case, reducing herewith the maintenance/intallation effort) a single Mantis installation in order to manage several projects. What do you think ? |
|