View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010920 | mantisbt | custom fields | public | 2009-09-09 11:20 | 2016-02-15 06:37 |
| Reporter | fxm | Assigned To | atrol | ||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Product Version | 1.1.7 | ||||
| Summary | 0010920: automatic number custom field | ||||
| Description | Hi, Is there any way to have an automatic number as custom field ? 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 | Example: Project 1 - issue 001 - order 001 | ||||
| Tags | No tags attached. | ||||
| related to | 0020605 | new | Secondary Key Issue counter automatically filled per "stable" project |
|
That won't work if you move issues between projects. |
|
|
You are right ... Thanks for your comment, this issue can be closed. François |
|
|
The only way I see this working is if we assign a new incremental ID to the ticket upon moving it to a new project. Then the original ID number from the donor project becomes a redirect to the new ticket in the new project. That said, I don't think it'll happen anytime soon. The reason being that no benefits have been identified. Are you able to come up with some detailed "user stories" that explain why this feature is needed? From there, it'd be up to someone with an interest in this feature actually writing the code to make it work. |
|
|
The only need from "the customer" is to have a continuous numbering in its issues by project. But I forget the "move" operation wich will always create a break in the sequence. So I think that this issue can actually been forgotten. Regards to all and thanks for your help and advices. |
|