| Issue Number | 3454 |
|---|---|
| Summary | [Summaries] Modify RLSO QC reports to display publish revision level in tan color |
| Created | 2011-11-21 11:06:40 |
| Issue Type | Improvement |
| Submitted By | Osei-Poku, William (NIH/NCI) [C] |
| Assigned To | Englisch, Volker (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2011-12-14 14:23:24 |
| Resolution | Won't Fix |
| Path | /home/bkline/backups/jira/ocecdr/issue.107782 |
BZISSUE::5148
BZDATETIME::2011-11-21 11:06:40
BZCREATOR::William Osei-Poku
BZASSIGNEE::Volker Englisch
BZQACONTACT::William Osei-Poku
In XMetal, Publish revision level changes are displayed with a tan background and font color. Please modify the Redline Strikeout QC reports to also display the same background and font color for Publish revision level changes. We can discuss this in our next CDR meeting especially if it will impact other filters.
BZDATETIME::2011-11-21 11:16:06
BZCOMMENTOR::Volker Englisch
BZCOMMENT::1
This is probably something that should be discussed with the board managers before it gets implemented.
As a note, please remember that the display in XMetaL is more
flexible than the display in the QC reports since the XMetaL display is
almost never printed while the output of the RS/BU reports is often
printed and submitted to the board members.
Also, there are fewer colors than one might expect that are usable and
equally distinguishable on different printers.
BZDATETIME::2011-12-02 09:31:26
BZCOMMENTOR::Robin Juthe
BZCOMMENT::2
Added [Summaries] to issue title. Plan to discuss this issue with Board managers at next CIS team meeting.
BZDATETIME::2011-12-09 15:18:17
BZCOMMENTOR::Volker Englisch
BZCOMMENT::3
I've looked through older Bugzilla issues and could not find any mention that the "publish" markup has ever been displayed in the same color as what is used in XMetaL. I wouldn't go as far as saying that it did not happen but I know from our publishing-markup spreadsheet that the colors hadn't changed in a very long time.
As we discussed at yesterday's status meeting this change is fairly involved since many of the global filters would need to be modified and it would certainly take many hours (I'm estimating around 20 hours) to implement the changes and do the testing.
William will check with the CIAT users to find out if the benefit of this change request would out-way the cost.
BZDATETIME::2011-12-14 14:23:24
BZCOMMENTOR::William Osei-Poku
BZCOMMENT::4
(In reply to comment #3)
>
> William will check with the CIAT users to find out if the benefit
of this
> change request would out-way the cost.
I have explained to CIAT staff that it would take several hours to make and QA the change and because this feature is rarely used, it was decided not to proceed with the changes.
Elapsed: 0:00:00.001756