Bug 869107 - Bug report URL flag to indicate "Revision of topic was specified in content spec"
Summary: Bug report URL flag to indicate "Revision of topic was specified in content s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: pressgang-ccms-dev
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-23 04:13 UTC by Joshua Wulf
Modified: 2014-10-19 23:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-07 01:29:41 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 838416 0 low CLOSED RFE: topic revision and ID as attributes of section 2021-02-22 00:41:40 UTC

Internal Links: 838416

Description Joshua Wulf 2012-10-23 04:13:07 UTC
At the moment the bug link text contains the topic ID and revision, however there is nothing to indicate to processor whether the revision number was specified in the Content Spec or is simply the latest revision at build time.

Can we add a flag to the bug link that is set when the topic revision number was specified in the content spec.

This is important for post-processors, such as the Deathstar, to correctly inject an edit link to the latest revision of a topic, or a read-only link to a specific revision of a topic.

Comment 1 Lee Newson 2012-11-12 03:23:19 UTC
Added for Version 0.28.0.

The Bug Link will now use the following syntax:

<ID>-<REVISION> <LAST MODIFIED> <LOCALE> [Latest]

or

<ID>-<REVISION> <LAST MODIFIED> <LOCALE> [Specified]

Comment 2 Lee Newson 2013-06-07 01:29:41 UTC
Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it.


Note You need to log in before you can comment on or make changes to this bug.