View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000782 | Bug Tracking | [All Projects] Feature Request | public | 2017-05-22 12:04 | 2017-06-09 20:50 |
| Reporter | jason | ||||
| Priority | none | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | no change required | ||
| Projection | none | ||||
| Product Version | [nofusscomputing.com] 2017 | Product Build | |||
| Target Version | Fixed in Version | 2.3.0 | |||
| Summary | 0000782: Add ability to log child tickets directly from an open ticket | ||||
| Description | Current practice is to raise a ticket and then use the relationships function: Child of Parent of Related to Is there a way to create "relationship" tickets directly from an open ticket. E.g if I have ticket 761 Open in my browser when I scroll to the relationships section it would be good to be able select a relationships and raise the new ticket from there. | ||||
| Tags | No tags attached. | ||||
| Stage | Complete | ||||
|
|
overall answer is no. this could be written into the code of mantis and would take a guesstimated 40-50hrs to complete (I would have to read the mantis bt code to find the best spot to put it). then every time mantis is updated that time would progressively increase for each update, if I was to add it. weighing up the benefits versus the effort, 50 odd hours against 30 seconds for an end user; not worth the time to invest. you can however request from the mantis development team the feature as they may be willing to write this feature in. see https://www.mantisbt.org/bugs/ |
|
|
Raised ticket 22916 with MantisBT |
|
|
Jon can you re-resolve? I am unable to |
|
|
correction to 0000782:0004294 after some research today it has been discovered that you can. if you click the clone button it will clone the current ticket including all fields. from there adjust as necessary including setting a relationship with the cloned ticket and click save. |
|
|
This ticket can be resolved as feature already exists |
|
|
Closing as requested |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-05-22 12:04 |
|
New Issue | |
| 2017-05-22 18:32 | Jon | Status | new => resolved |
| 2017-05-22 18:32 | Jon | Resolution | open => no change required |
| 2017-05-22 18:32 | Jon | Fixed in Version | => 2.3.0 |
| 2017-05-22 18:32 | Jon | Stage | => Complete |
| 2017-05-22 18:32 | Jon | Note Added: 0004294 | |
| 2017-05-23 07:41 |
|
Status | resolved => feedback |
| 2017-05-23 07:41 |
|
Resolution | no change required => reopened |
| 2017-05-23 07:41 |
|
Note Added: 0004301 | |
| 2017-05-23 07:42 |
|
Note Added: 0004302 | |
| 2017-05-23 07:42 |
|
Status | feedback => new |
| 2017-05-23 16:54 | Jon | Note Added: 0004303 | |
| 2017-05-29 15:50 |
|
Note Added: 0004374 | |
| 2017-06-09 20:50 | Jon | Status | new => resolved |
| 2017-06-09 20:50 | Jon | Resolution | reopened => no change required |
| 2017-06-09 20:50 | Jon | Note Added: 0004440 |
