-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
1
-
Currently any change to the epic color field in Jira is sent as a notification with the Jira color code and the color change highlighted in the background of the ghx-label number
Epic Colour: | ghx-label- 7 2 |
---|
The background color on the color code is not discernible.It would be more meaningful to convey the color change as
Epic Colour : Changed from Purple to Green
since in some organizations, teams have color conventions around Epics.
[JSWSERVER-16407] Epic color changes in JIRA should be conveyed meaningfully in sent notifications
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3069679 ] | New: JAC Suggestion Workflow 3 [ 3662618 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2627916 ] | New: JAC Suggestion Workflow [ 3069679 ] |
Support reference count | New: 1 |
Description |
Original:
Currently any change to the epic color field in Jira is sent as a notification with the Jira color code and the color change highlighted in the background of the ghx-label number
||Epic Colour:|ghx-label- 7 2| The background color on the color code is not discernible..It would be more meaningful to convey the color change as {code:java} Epic Colour : Changed from Purple to Green{code} since in some organizations, teams have color conventions around Epics. |
New:
Currently any change to the epic color field in Jira is sent as a notification with the Jira color code and the color change highlighted in the background of the ghx-label number
||Epic Colour:|ghx-label- 7 2| The background color on the color code is not discernible.It would be more meaningful to convey the color change as {code:java} Epic Colour : Changed from Purple to Green{code} since in some organizations, teams have color conventions around Epics. |
Hi,
Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.
To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.
Regards,
Jira Server and Data Center Product Management