| Summary: | RFE: Make "Report a bug" link text configurable | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] PressGang CCMS | Reporter: | Joshua Wulf <jwulf> | ||||
| Component: | Web-UI | Assignee: | pressgang-ccms-dev | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 1.x | CC: | topic-tool-list | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | --- | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Created attachment 564799 [details]
Screenshot of styled bug link
The css will need to be absorbed into the brands via separate bugs, but the "What's wrong with this?" wording would need to be done in Skynet. <rudi> JBoss -- open a bug against the brand package for the EngServices brand, a ticket in engineering-services queue assigned to rlerch |
Since logging a bug is an edge case (not everyone will do it) and it is "meta-content", it needs to be separated from the visual hierarchy of the information content. In the attached screenshot you can see the link reduced in size (edge case, not as relevant as the other content) and moved to the right (meta-function). Here's the common.css to achieve this: div.RoleCreateBugPara { text-align: right; font-size: 0.5em; } I've also changed the text in the screenshot from "Report a Bug" to "Something wrong with this?" Since the goal is to solicit feedback, it's worded from the user's perspective. "Something wrong with this?" is larger on the screen than "Report a Bug", which makes more visual clutter, but it speaks to a wider audience with the same message; i.e: anyone who understands "Report a Bug" will understand it, whereas the converse is not true. Some people will understand to click "Something wrong with this?" who will not make the same connection with the message "Report a Bug".