Bug 1022052 - Cannot set JIRAVersion when JIRAComponent is not specified
Summary: Cannot set JIRAVersion when JIRAComponent is not specified
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 1.3
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-22 14:41 UTC by Petr Penicka
Modified: 2014-01-13 08:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-03 22:16:28 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Petr Penicka 2013-10-22 14:41:56 UTC 
In CS22448, the dev team has decided that the JIRAComponent field should be empty in direct bug report links. This is because the book is not related to any of the components in WFK, and it does not make sense to create an OpenShift component just for this purpose.

When I remove the JIRAComponent property from the content specification, I get the following validation error message:

  ERROR: A JIRA Component must be specified to set a Version.
  ERROR: The Content Specification is not valid.

This does not make much sense to me as the version is not the component version, but the product (WFK) version.

Could it please be made possible to specify an empty JIRAComponent and still have JIRAVersion?
Comment 1 Lee Newson 2013-11-05 02:53:51 UTC 
Fixed in 1.3-SNAPSHOT build 201311051246

This was just a copy from the BZ check (which was also incorrect), as such I've removed the check that a component must exist to specify a version.
Comment 2 Lee Newson 2013-11-07 04:14:39 UTC 
This version is now live on the dev/test server.
Comment 3 Matthew Casperson 2013-11-24 21:28:23 UTC 
Confirmed that both BZVersion and JIRAVersion can be specified without BZComponent or JIRAComponent.
Note You need to log in before you can comment on or make changes to this bug.