Re: [jbpm-dev] jira affect/s version fields?
Marco,
That should be the release that the problem occurs on. So it should
refer to one of the past releases. Sometimes people put in jBPM 5.3
when creating the bug, but since that hasn't been released yet, that
doesn't really make sense I think, so I sometimes remove that ;)
Kris
On 05/04/2012 10:12 PM, Marco Rietveld wrote:
Hi Kris,
What should we use the jira "affects version/s" field for in jira?
I noticed that you cleared the field on a couple bugs. :)
Thanks,
Marco
24-04-12 11:56, Kris Verlaenen (JIRA):
> [
>
https://issues.jboss.org/browse/JBPM-3585?page=com.atlassian.jira.plugin....
> ]
>
> Kris Verlaenen updated JBPM-3585:
> ---------------------------------
>
> Fix Version/s: jBPM 5.x
> Affects Version/s: (was: jBPM 5.x)
>
>
>> jbpm-bpmn2 test fail with JPA 2/Hibernate 4
>> -------------------------------------------
>>
>> Key: JBPM-3585
>> URL: https://issues.jboss.org/browse/JBPM-3585
>> Project: jBPM
>> Issue Type: Bug
>> Security Level: Public(Everyone can see)
>> Components: Persistence, Runtime Engine
>> Reporter: Marco Rietveld
>> Assignee: Marco Rietveld
>> Fix For: jBPM 5.x
>>
>>
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators:
> https://issues.jboss.org/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>