View Issue Details

IDProjectCategoryView StatusLast Update
0024732mantisbtuipublic2018-09-29 03:51
Reporterpromat Assigned Toatrol  
PriorityhighSeverityminorReproducibilityalways
Status closedResolutionduplicate 
Product Version2.14.0 
Summary0024732: Assigning Tickets to nobody is not possible on "View Issues" page
Description

Hey,

I would like to assign more than one ticket on the "View Issues" page to nobody. This is not possible. When I mark one or more tickets on the "View Issues" Page and choose "Assign" I cannot choose "Nobody". Directly in a ticket it is possible to choose "Nobody" so I think it should also be possible for more than one ticket.
I would really appreciate if you fix this and make this a change in the next main Mantis Version.

Thank you.

BR

Steps To Reproduce

Mark one or several tickets on the "View Issues" Page and choose "Assign"

TagsNo tags attached.
Attached Files
mantisbug.PNG (13,558 bytes)   
mantisbug.PNG (13,558 bytes)   

Relationships

duplicate of 0021640 acknowledged Assign Group Action doesn't support un-assigning 

Activities

promat

promat

2018-09-19 03:50

reporter   ~0060668

Hi,
Atrol, could you please reopen this ticket. Actually this should be the ticket to work on, because in the other tickets which are "dupes" it is written, that this is a "feature wish"... but actually this is a bug, which should be fixed with higher priority than a "feature wish". When I click on one specific ticket, it is possible to change the handler to nobody. This means, it was planned by the mantis developers to make it possible to assign tickets to nobody. So why should it not be possible for more than one ticket? This makes no sense, thats why i consider this to be a bug, which I hope can be fixed in one of the previous mantis version.

I would really appreciate if you could fix this and thank you for Mantis which is really nice.

BR

atrol

atrol

2018-09-19 15:09

developer   ~0060670

Our process to triage issues is to resolve newer issues as duplicates of older ones.
It does not depend on the severity or priority that the reporter has set.

I don't think this is a bug, as

  • it never worked before
  • there is no documented functionality for it

Of course, it does not matter if it's a bug or a feature request.
It all depends on priority (which is high for you but not that high for the Mantis product in general) and a developer or community member deciding to spend their time on a specific issue.

Submitting a patch is always a good idea, as it increases the chances of improvement eventually making it into MantisBT core. All contributions are welcome and greatly appreciated.

Patch submissions can be made in several ways. In the order of preference:

  1. Send us a Pull Request on our Github repository [1]
  2. Attach a GIT patch to the issue
  3. Attach a Unified Diff, clearly specifying the patch's base release

Kindly avoid to upload entire modified PHP files.

Please make sure that your submissions adhere to our Coding Guidelines [2], if they don't your patch might be rejected.

[1] https://github.com/mantisbt/mantisbt
[2] http://www.mantisbt.org/wiki/doku.php/mantisbt:coding_guidelines