Bug 584957
| Summary: | 1.1.6: Support selecting more than one component per bug report | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | David Lawrence <dkl> | ||||
| Component: | Creating/Changing Bugs | Assignee: | Simon Green <sgreen> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 3.6 | CC: | 8ru2u4gz, agk, atangrin, dgregor, ebaak, kbaker, ldimaggi, lpetrovi, max.andersen, mharvey, mkanat, nelhawar, rrajasek, sgreen, tkirby | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-05-20 04:26:51 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 583097, 584954, 694046 | ||||||
| Attachments: |
|
||||||
|
Description
David Lawrence
2010-04-22 19:19:11 UTC
I'd go with the "create an additional field" method. You could add the Assignee and QA Contact of the additional components to the CC list. Again we have the problem with having multiple custom fields, one per product due to different values for each, and then having an ever growing boolean charts drop down. And also the two list would need to be kept in sync through changes to editcomponents.cgi. Unless there is code hacks to keep the custom fields empty and the UI pulls the component list from the core component field and dynamically fills in the extra components drop down. But that still doesn't help the boolean charts issue. Okay. Like I mentioned in the other bug, probably the best solution is allowing multi-value value controllers. Also commented in the other bug about this as well. Assigned to Trevor to verify/QA. https://bz-web2-test.devel.redhat.com/ You can select a single componet or additional components using the Extra Components custom field. The lists should be the same. The JIRA issues migrated should have these fields populated properly. Assigning this to Max to review. Len and I looked at this feature. The Extra Components custom field feature "as coded" tested and works fine...we did not find any bugs. I have to say...in reading the original requirements...they are not very clear to me, so I cannot say that this feature meets the requirements. The solution delivered is clear to me. Hey Mike. When you say the "original requirements", are you actually reading the Requirements Document that Everything Solved produced for Red Hat? Because that's where the requirements would be. Hi Max Kanat-Alexander, I'm referring to : https://engineering.redhat.com/trac/bugzilla/wiki/JiraMigrationRequirements line item 1.1.6. My note was to Max Andersen (JBDS) Dev Tech lead. He was actually involved in the origination of 1.1.6. Max Andersen, Can you look at this feature and comment when you have a chance? https://bz-web2-test.devel.redhat.com/ If you feel it does not meet the requirement, then please change the Status back to "Assigned" and clearly state the requirement that has not been met. If all requirements are met, then please change the status to "verified." Thanks. Just as a status report on this. I am trying to work the code in such a way to allow just selecting multiple components/versions in the standard Bugzilla version fields when viewing the bug in show_bug.cgi or entering a new bug with enter_bug.cgi. To accomplish this I am having to backport some changes from the upstream 4.0 version (set_all functionality) and is why it is taking slightly longer than expected. I am doing this to make the UI more intuitive and it is utilizing the work down also by the contractor for the JIRA requirements. Most of the hard stuff will be done in the background and the user will just need to use the version and component fields as if they are multi select. You can sort of see this working now on bz-web2-test.devel.redhat.com by entering a new bug report, select multiple version/components and then commit. I will leave it ON_QA so that Max Anderson can take a look at what is there so far but it is not 100% working yet. Thanks Dave Created attachment 468700 [details]
Patch with work so far for multiple versions/components support (v1)
Simon/Noura. Here is a patch from work to date on this bug and the other related bug (multiple component support) that I was almost complete. I have to backport some code from the upstream (4.0) that has a proper Bugzilla::Bug->set_all to allow this work as expected. When this is complete, it should allow for the version and component fields to be multi select fields and then split the values in the backend to the extra custom fields. It is using extension hooks to do most of the work as done by our BZ contractor. Please email me at dklawren for any more info on this if you get stuck or whatever.
Take care
Dave
I consider this resolved. Was this implemented? I appear not to be able to add more than 1 component to new reports of mine. |