Open Bug 460286 Opened 17 years ago Updated 12 years ago

Implement Param.set() to set parameters from webservices

Categories

(Bugzilla :: WebService, enhancement, P2)

enhancement

Tracking

()

People

(Reporter: LpSolit, Unassigned)

Details

Bug 443210 is about getting current parameters, this one is about setting them. This would greatly help doing QA, btw. ;) I was thinking about this API: Param.get('param_name'); Param.set('param_name', $value); This would be very easy to use.
We'd want Param.set({ param_name => $value, other_param => $other_value }), probably.
Priority: -- → P2
too late for 3.4.
Target Milestone: Bugzilla 3.4 → Bugzilla 4.0
Target Milestone: Bugzilla 4.0 → Bugzilla 3.6
We no longer accept new features for Bugzilla 3.6. Retargetting to 3.8.
Target Milestone: Bugzilla 3.6 → Bugzilla 3.8
Target Milestone: Bugzilla 4.0 → Bugzilla 5.0
Assignee: webservice → dkl
(In reply to Max Kanat-Alexander from comment #1) > We'd want Param.set({ param_name => $value, other_param => $other_value }), > probably. For consistency with bug 443210, which implemented Bugzilla.parameters, I suggest: Bugzilla.set_parameters({ param_name => $value, other_param => $other_value }) dkl, are you actively working on this? Else I could do it.
(In reply to Frédéric Buclin from comment #4) > (In reply to Max Kanat-Alexander from comment #1) > > We'd want Param.set({ param_name => $value, other_param => $other_value }), > > probably. > > For consistency with bug 443210, which implemented Bugzilla.parameters, I > suggest: > > Bugzilla.set_parameters({ param_name => $value, other_param => $other_value > }) > > dkl, are you actively working on this? Else I could do it. If you want to work on it, then I feel free to take it. I have plenty to do currently. I did want to work on it back then but never was able got back to it and I would need to finish up some other things first. dkl
OK, so taking.
Assignee: dkl → LpSolit
Status: NEW → ASSIGNED
We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved. I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.
Target Milestone: Bugzilla 4.4 → ---
Assignee: LpSolit → webservice
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.