This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 320202 - add support for use... administration parameters
Summary: add support for use... administration parameters
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.5   Edit
Assignee: Frank Becker CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 322867 324007
Blocks: 307729 317682
  Show dependency tree
 
Reported: 2010-07-18 16:35 EDT by Frank Becker CLA
Modified: 2011-02-10 15:58 EST (History)
3 users (show)

See Also:


Attachments
patch V1 (14.67 KB, patch)
2010-07-21 14:41 EDT, Frank Becker CLA
eclipse: review?
Details | Diff
mylyn/context/zip (26.01 KB, application/octet-stream)
2010-07-21 14:41 EDT, Frank Becker CLA
no flags Details
settings page (19.51 KB, image/png)
2010-07-27 16:22 EDT, Steffen Pingel CLA
no flags Details
patch V2 (17.19 KB, patch)
2010-08-09 15:50 EDT, Frank Becker CLA
no flags Details | Diff
mylyn/context/zip (18.59 KB, application/octet-stream)
2010-08-09 15:50 EDT, Frank Becker CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Becker CLA 2010-07-18 16:35:34 EDT
Actual there is now way to get the ../editparams.cgi?section=bugfields fields from config.cgi or webservice method.

We can fields in RepositoryConfiguration that can hold the information for 
* useclassification
* usetargetmilestone
* useqacontact
* usestatuswhiteboard
* usebugaliases
* use_see_also

RepositoryTemplate genericAttributes can hold the values so we are able to support the correct values for eclipse.org.

BugzillaRepositorySettingsPage should show and edit the fields.

SWe then can use the  RepositoryConfiguration for correctly show the correct field in TaskEditor

see bug#307729 

Thoughts?
Comment 1 Steffen Pingel CLA 2010-07-19 13:35:52 EDT
Does it make sense to request to get it added to the Bugzilla configuration? I have removed the milestone for now since we have no clear solution for this bug.
Comment 2 Frank Becker CLA 2010-07-19 13:55:37 EDT
(In reply to comment #1)
> Does it make sense to request to get it added to the Bugzilla configuration? I
> have removed the milestone for now since we have no clear solution for this
> bug.

Sorry my fault the target should be 3.5.

I think we should do this and not wait until 

https://bugzilla.mozilla.org/show_bug.cgi?id=557183
and
https://bugzilla.mozilla.org/show_bug.cgi?id=443210

(see target milestone)
Comment 3 Steffen Pingel CLA 2010-07-19 14:53:34 EDT
Makes sense. I'll assign this to you then :).
Comment 4 Frank Becker CLA 2010-07-21 14:41:36 EDT
Created attachment 174898 [details]
patch V1

Rob,
Steffen,

please review this patch.

Or should I commit this to HEAD?

The following is included.

* UI in BugzillaRepositorySettingsPage
* support to define the values in the RepositoryTemplate
* set the repository values from the template when they not exists in the repository (migrate)
Comment 5 Frank Becker CLA 2010-07-21 14:41:39 EDT
Created attachment 174899 [details]
mylyn/context/zip
Comment 6 Frank Becker CLA 2010-07-26 03:08:11 EDT
I commit the patch so that I can fix bug 317682 and bug 307729
Comment 7 Steffen Pingel CLA 2010-07-27 16:22:32 EDT
Created attachment 175354 [details]
settings page
Comment 8 Mik Kersten CLA 2010-07-29 13:37:55 EDT
I suggest removing "autodtect workflow" and always detecting it, or at least making it be on by default.
Comment 9 Steffen Pingel CLA 2010-07-29 14:24:50 EDT
We reviewed the UI in the last meeting and discussed the following suggestions:
* Change the label of the group to "Task Editor Attributes to Suppress"
* Use the labels of the actual attributes, e.g. "Target Milestone" instead of "usetargetmilestone"
* Reverse the logic, i.e. checking an attribute should hide it

What is the purpose of useclassification is that used anywhere in Mylyn? If not, it's probably best to remove it.
Comment 10 Frank Becker CLA 2010-08-09 15:50:17 EDT
Created attachment 176184 [details]
patch V2

(In reply to comment #9)
> We reviewed the UI in the last meeting and discussed the following suggestions:
> * Change the label of the group to "Task Editor Attributes to Suppress"
> * Use the labels of the actual attributes, e.g. "Target Milestone" instead of
> "usetargetmilestone"
> * Reverse the logic, i.e. checking an attribute should hide it
> 
> What is the purpose of useclassification is that used anywhere in Mylyn? If
> not, it's probably best to remove it.

This is all fixed!
Comment 11 Frank Becker CLA 2010-08-09 15:50:19 EDT
Created attachment 176185 [details]
mylyn/context/zip
Comment 12 Frank Becker CLA 2010-08-09 15:58:09 EDT
(In reply to comment #8)
> I suggest removing "autodtect workflow" and always detecting it, or at least
> making it be on by default.

Mik,

I think we should discuss this.

I see the following problems:

1) XMLRPC is only valid for Bugzilla versions >= 3.6
2) XMLRPC need some additional packages to install

So for me I think it is not possible to turn it on by default.

Thoughts?
Comment 13 Steffen Pingel CLA 2011-02-05 16:46:43 EST
Frank, where are we at with this?
Comment 14 Frank Becker CLA 2011-02-10 15:58:47 EST
(In reply to comment #13)
> Frank, where are we at with this?

I think we can close this. Mik if you think we should remove "autodtect workflow" we can create an other bug for this.