Question on the affectedVersion data search in Jira Server

[Suhas Shastry]

Hi,

I would like to ask a question on the affectedVersion field usage in the JQL search. Are these JQL searches are based on the created date of the Release Version in the Release section or is it based on the internal release ID?

For example,

I have "Release A" "Release B" "Release Aa" "Release C" versions created in the Release section in the order mentioned before. The "Release Aa" is a dependent or we can call it as a maintenance release of "Release A". And my JQL is trying to fetch the Issues <= "Release B". Which mean that the issues with affectedVersions having values "Release A" "Release B" "Release Aa" should be listed. At this point for me, the issues having affectedVersion "Release Aa" are not listed. 

JQL: affectedVersion <= "Release B"

Hence the question here is, are the search results are based on the release Created date in Jira or the internal ID associated with the Version?

Please let me know if I have to provide any other details. Looking forward for a quick response from the Atlassian or Community experts.

Thanks in advance!!

[Shivaprasad Hattaraki · Accepted solution]

I have used behaviour script for this.. 

steps 1: Add behaviour 

          2: Add field ex: Epic Link

              And paste the script in server side script 

         3: Add mapping Ex: projects and issue types and SAVE. 

//Script 

if(getAction() == null){

    getFieldById(getFieldChanged()).setRequired(true)

}else{

    getFieldById(getFieldChanged()).setRequired(false)

}

[Tarun Sapra]

Hello @Shivaprasad Hattaraki

If you are fine with epic link being mandatory in both create and edit screen then you dont' need any plugin for it. Just make the field mandatory in the field configuration which is associated with the issueType having the Epic link field.

[Tarun Sapra]

https://confluence.atlassian.com/adminjiraserver0711/specifying-field-behavior-955168173.html

"Making a field required"

[Jagriti]

@Tarun Sapra 

Hi

Is it possible to make "epic Link" field mandatory in this way .

I want it mandatory for story (child of epic) 

But under configuration schemes , Epic link is "locked" no way to make this mandatory from here .

any suggestions?

[Michael Aglas]

it is not possible for Epic Link field

I think otherwise this questions wouldn't been raised

[Matthias Gaiser _K15t_]

Hi @Shivaprasad Hattaraki,

I've found this question and answer by other users which might help you.

On the other hand: Does it need to be in the edit screen or is the create screen also fine? You could follow this JIRA Knowledgebase article how to do this with a validator on the create transition.

Cheers,
Matthias.

[Shivaprasad Hattaraki]

It is fine with both create and edit screen.