Open
Bug 103587
Opened 23 years ago
Updated 5 years ago
Enter and display keywords like dependency list
Categories
(Bugzilla :: Creating/Changing Bugs, enhancement, P3)
Tracking
()
REOPENED
People
(Reporter: asa, Unassigned, Mentored)
References
Details
The keywords should be listed in bugs like dependencies so that all of them are visible without select scrolling in the textfield. Right now b.m.o has an average keyword length of about 7 characters. We insert a comma and a space between each keyword. That works out to about 9 characters per displayed keyword. The field for keywords is about 60 characters long. So on average we can fit between 6 and 7 keywords in the visible space. This isn't sufficient, especially if we continue to eat up that space with keywords to track project management decisions instead of the more functional and queryable meta/tracking bug system. ("nsenterprise+, nsbranch+, mozilla0.9.5, nsdogfood-, mozilla1.0" leaves zero room for keeping other keywords like crash, regression and dataloss in the viewable area of the textfield) The keyword entry and display mechanism should be like the dependency entry and display.
Updated•23 years ago
|
Severity: normal → enhancement
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.20
Updated•22 years ago
|
OS: Windows 2000 → All
Hardware: PC → All
Updated•21 years ago
|
Summary: [RFE] enter and display keywords like dependency list → Enter and display keywords like dependency list
Comment 1•20 years ago
|
||
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Assignee: myk → create-and-change
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
This has since been corrected.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Comment 3•10 years ago
|
||
Not true. They are still listed in the text field.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 4•10 years ago
|
||
(In reply to FrΓ©dΓ©ric Buclin from comment #3) > Not true. They are still listed in the text field. I agree it would be nice for it show the current keywords set and an (edit) link next to it similar to URL, blocks and depends on. So we can leave this open and see if someone wants to pick it up. dkl
Whiteboard: [good first bug]
Comment 5•10 years ago
|
||
:dkl- is this still a worthwhile bug to fix? If so, and if this makes a good first bug, can you link to the code, how to reproduce this problem, and what an ideal fix looks like? This should have a mentor assigned as well.
Flags: needinfo?(dkl)
Comment 6•10 years ago
|
||
(In reply to Joel Maher (:jmaher) from comment #5) > :dkl- is this still a worthwhile bug to fix? If so, and if this makes a > good first bug, can you link to the code, how to reproduce this problem, and > what an ideal fix looks like? This should have a mentor assigned as well. I believe so. I can see where entering a lot of keywords for a single bug would look bad as the text field doesn't change depending on the number selected. Assigning myself as a potential mentor. dkl
Mentor: dkl
Flags: needinfo?(dkl)
Comment 7•10 years ago
|
||
Hey David, I would like to work on this bug. Can you help me with getting the repository? Thank You~
Flags: needinfo?(dkl)
Comment 8•10 years ago
|
||
(In reply to Vaibhav Bhosale from comment #7) > I would like to work on this bug. Can you help me with getting the > repository? First off, thank you for your intent to contribute to Bugzilla! It's very much appreciated and needed. Before dkl gets around to help you more specifically, you can start by going through developer resources at https://www.bugzilla.org/developers/. More specifically, the step 4 of Contribution Guide (the first link on the previous page) at https://wiki.mozilla.org/Bugzilla:Developers points to a page detailing how you can use git to clone Bugzilla repository.
Comment 9•10 years ago
|
||
Like wicked said, the wiki is a good starting point. Please try those steps and let me know if you run into any issues. There is also a docker image with Bugzilla pre-installed that can be used as a development environment. https://registry.hub.docker.com/u/dklawren/docker-bugzilla/ https://github.com/dklawren/docker-bugzilla https://wiki.mozilla.org/BMO/DeveloperBox dkl
Flags: needinfo?(dkl)
Updated•7 years ago
|
Keywords: good-first-bug
Comment 10•7 years ago
|
||
Having a look into this now. Am I right in thinking your just trying to reformat the key word box to fit more keywords and display them in a decent way?
Flags: needinfo?(asa)
Comment 11•7 years ago
|
||
A rough idea where the code is located would also be handy please, there are a lot of file in here.
Comment 12•6 years ago
|
||
Removing good-first-bug
keyword because team does not have bandwidth to mentor at the moment.
Keywords: good-first-bug
Reporter | ||
Updated•5 years ago
|
Flags: needinfo?(asa)
Updated•5 years ago
|
Whiteboard: [good first bug]
You need to log in
before you can comment on or make changes to this bug.
Description
•