Page 1 of 1

Save custom field values on Updating an issue

Posted: 01 Feb 2007, 15:22
by phpchris
Hi folks, as it sais above.
I made a custom field with a list of our customers.
Sometimes I need to relate an issue to the customer, but when I update the problems state, the value of the custom field is set to blank again.
Has anyone the same problem or maybe even a solution?

Posted: 01 Feb 2007, 17:36
by Narcissus
What version are you using? I seem to recall this being an issue that was addressed in one of the latest releases, but I'm not too sure...

Posted: 02 Feb 2007, 07:27
by phpchris
I am using version 1.0.5.
Is there a changelog or so anywhere?

Posted: 02 Feb 2007, 12:26
by Narcissus

Posted: 02 Feb 2007, 14:33
by phpchris
Cant seem to find it anywhere there :(
Have you seen anything like this?

Posted: 02 Feb 2007, 15:25
by Narcissus
Oops, my bad.

Maybe it was just mentioned somewhere along the way... as opposed to actually being resolved.

It seems as though there are a number of unresolved issues pertaining to this kind of a workflow.

Sorry!

Posted: 12 Feb 2007, 07:54
by phpchris
No worries...

How can I help in this issue? Where are the files and things to start at?

Posted: 26 Feb 2007, 15:09
by phpchris
Anyone?

Posted: 27 Feb 2007, 18:05
by Narcissus
Firstly, I would suggest grabbing the latest code from the repository and see if the problem still exists. If it does, I would guess that the best file to start looking in is bug_update.php. Also check mantisbt.org/bugs to see if the problem as been reported / commented on.

Unfortunately my dev environment has been AWOL for some time so that's about as much as I can tell you ATM :(

ouch...a triage killer

Posted: 09 Mar 2007, 00:21
by vavoom
i checked the bug list searching for 'update custom' and returned what looked to be unrelated issues.

since this is really painful to triage teams (or anyone that might use the Update button) how can we try and bubble it up to the top of the list?

Thanks

Posted: 09 Mar 2007, 01:29
by ed
Report the issue at http://www.mantisbt.org/bugs/

You can then hope that 'someone' will work on the issue or to try and bubble it up, you can offer money via the sponsorship button.

Posted: 09 Mar 2007, 05:59
by vboctor
I've tested this on the latest code but was unable to reproduce the problem. Can you please report a bug with the steps to reproduce? Also include the following:

1. What kind of custom field is it?
2. Does the user updating the issue has access to update the custom field?
3. Does the original value in the custom field still a valid value for it?

Posted: 12 Mar 2007, 13:26
by phpchris
vboctor wrote: 1. What kind of custom field is it?
In my case it is a list with customer names
I don't know how it is called in english, since I use german language.
vboctor wrote: 2. Does the user updating the issue has access to update the custom field?
No, he does not need to update anything at all.
The thing is that the value is not selected in the combobox and it will save the first value of the list.
vboctor wrote: 3. Does the original value in the custom field still a valid value for it?
Yes...

Posted: 21 Mar 2007, 09:26
by phpchris
*bump*