View Issue Details

IDProjectCategoryView StatusLast Update
0016454mantisbtotherpublic2020-09-05 06:20
Reportergwijngaarden Assigned Todregad  
PrioritynormalSeverityminorReproducibilityN/A
Status assignedResolutionopen 
Product Version1.2.15 
Summary0016454: Missing something with $g_reassign_on_feedback
Description

I'm trying to let this variable work with other users than only the reporter. Is this possible in anyway as the documentation only talks about the reporter.

TagsNo tags attached.

Relationships

related to 0004469 acknowledged "Reply To Feedback" Button 
related to 0027237 new "feedback" status becomes "new" when a note is added 

Activities

dregad

dregad

2013-10-04 11:20

developer   ~0038207

Unfortunately not in the present state, the feature only works with original reporter.

I started working on a feature branch going along the lines of what you want to do about a year ago, you might be interested in checking out. Note that I have not touched it since then, and I'm not sure in what state it's in (it might not work).

Anyway let me know your feedback.

gwijngaarden

gwijngaarden

2013-10-07 02:37

reporter   ~0038214

Last edited: 2013-10-07 02:37

View 2 revisions

Thanks for the reply. Can you show me where I can find this branch? It might be worth a try for my organisation.

dregad

dregad

2013-10-07 04:13

developer   ~0038218

Apologies, I forgot the link... Here it goes

https://github.com/dregad/mantisbt/tree/feedback-prev-stat

gwijngaarden

gwijngaarden

2013-10-16 09:31

reporter   ~0038276

We looked at it but implementing this would mean that we can't update. Is it possible to contact you personally about this?

dregad

dregad

2013-10-17 04:05

developer   ~0038286

Not sure what you mean by contacting me personally.

Did you test the feature at all ? If yes, I would appreciate your feedback. If you found no issues with it and it satisfies the requirement, I will consider implementing it in the next release of Mantis.

gwijngaarden

gwijngaarden

2013-10-17 06:56

reporter   ~0038289

Thanks for your reply.

Well we do have to test but it is something we would like to see implemented in a next release. We'll check and come back to it.

dregad

dregad

2014-01-23 12:29

developer   ~0039154

@gwijngaarden did you ever get around to testing this ? Let me know your results.

gwijngaarden

gwijngaarden

2014-01-24 03:15

reporter   ~0039157

Last edited: 2014-01-24 03:16

View 2 revisions

Thanks for your inquiry. Due to circumstances I didn't have the time to test it yet because I have to ask somebody to install this and he didn't have the time yet to do this. Hopefully somewhere in the near future. It's still on my radar.

gwijngaarden

gwijngaarden

2016-04-04 11:21

reporter   ~0052904

@dregad I tried this option but alas. When another user than the reporter comments on a bug the status stays on feedback. What am I doing wrong?

dregad

dregad

2016-04-06 09:36

developer   ~0052914

I have not looked at this code for a long time, but if I remember correctly it implements the following behavior, when an issue is in Feedback state:

  • if user is original reporter: the "add note" section shows a "provide feedback" button which adds the note and changes status
  • for other users, there are 2 buttons available, the "provide feedback" one as described above, and a regular "add note" button which does just that without changing issu status.

In addtion, and that was the original fix I was targeting with that feature branch, the issue status should change back to what it was prior to entering "feedback" state, as opposed to just going back to "new" as it currently does (see 0004469)

gwijngaarden

gwijngaarden

2016-04-08 03:32

reporter   ~0052919

Thanks for the speedy reply. The behavior you're describing is not exactly what we're looking for.

It seems the behavior described in 0004469 almost matches the thing we want. Unfortunately the status of an issue is only reverted back to ASSIGNED if the reporter adds a note. We want that the status is always reverted back to ASSIGNED if a note is added to an issue which has the status FEEDBACK. So not only the reporter.

Could something be realized that creates this behavior in Mantis?

Issue History

Date Modified Username Field Change
2013-10-04 07:47 gwijngaarden New Issue
2013-10-04 11:20 dregad Note Added: 0038207
2013-10-04 11:20 dregad Status new => feedback
2013-10-07 02:37 gwijngaarden Note Added: 0038214
2013-10-07 02:37 gwijngaarden Status feedback => new
2013-10-07 02:37 gwijngaarden Note Edited: 0038214 View Revisions
2013-10-07 04:13 dregad Note Added: 0038218
2013-10-07 04:13 dregad Assigned To => dregad
2013-10-07 04:13 dregad Status new => feedback
2013-10-16 09:31 gwijngaarden Note Added: 0038276
2013-10-16 09:31 gwijngaarden Status feedback => assigned
2013-10-16 09:31 gwijngaarden Note View State: 0038276: private
2013-10-16 09:31 gwijngaarden Note View State: 0038276: public
2013-10-17 04:05 dregad Note Added: 0038286
2013-10-17 04:05 dregad Status assigned => feedback
2013-10-17 06:56 gwijngaarden Note Added: 0038289
2013-10-17 06:56 gwijngaarden Status feedback => assigned
2014-01-23 12:29 dregad Note Added: 0039154
2014-01-24 03:15 gwijngaarden Note Added: 0039157
2014-01-24 03:16 gwijngaarden Note Edited: 0039157 View Revisions
2016-04-04 11:21 gwijngaarden Note Added: 0052904
2016-04-06 09:36 dregad Note Added: 0052914
2016-04-06 09:36 dregad Relationship added related to 0004469
2016-04-08 03:32 gwijngaarden Note Added: 0052919
2020-09-05 06:20 dregad Relationship added related to 0027237