Smart value use of "{{#if ... }} does not seem to work

[Richard Bos]

Which Jira-server version supports the use of smart value: "{{#if ... }}  text {{/}}, or is this a Jira-cloud only functionality ?

I would like to use this in a reminder email, that is sent to two people, using as source two different people fields.  However sometimes the two fields holds the same person, resulting in an email with twice the same name.  That looks a little odd.

To prevent this, I thought let's use this construct:

{{#if(issue.assignee.equals(issue.coordinator))}}
  Name 1,
{{/}}

But this does not work.

the {{#if  }} is shown here:

• New automation smart values in Jira Cloud 
• smart-values-lists 

But it looks like functionality for the Jira cloud version.

Is there a way to similar functionality in Jira-Server?

[Nic Brough -Adaptavist- · Accepted solution]

The most likely explanation is that your "workflow post function to get assignee filed values from parent" does not index the sub-tasks.  It needs to do that.

[Omprakash Thamsetty]

@Nic Brough [Adaptavist] I have already doing the index in workflow post function. Please see below screen shot. I am unable to change the positions. Anything I am missing here?

I have limited access to update the comment in this forum. I need to get 2 points to get unlimited access.

workflow_postFunction_reindex.jpg

[Nic Brough -Adaptavist-]

It's the same answer - your sub-tasks look like they are not being indexed. Let's test that rather than going around in circles - run the transition, check that the search fails as per your original question, then make a minimal edit to *the subtask* (stick a . on the end of a text field, change the reporter etc). Avoid touching any of the four fields you have copied though, that could complicate tracing what is happening. Once you've made a change, try the original test again - does it work this time?

[Omprakash Thamsetty]

@Nic Brough [Adaptavist] Your test work fine. I have followed below steps and showing the original search.

1) Ran the transition

2) edited in comment section and then updated it.

3) Tried searching in filter with original posted in this forum question. Its showing 1 issue record but there is another 2 issues. So What I need to do once the sub-task been created in workflow post function to fix the issue?

Here is the screen shots for reference

sub_task_search.jpg

Total sub-task 3. The old 2 sub-task which are posted in original question in this forum not showing.

What should I do once the sub-task created to do indexing ?

[Nic Brough -Adaptavist-]

Sorry, I need the test result clarifying. You are saying that: 1) You ran the transition 2) You ran the search and got 0 results 3) You did a minor edit 4) You ran the search and got 1 result Is that correct?

[Omprakash Thamsetty]

@Nic Brough [Adaptavist] yes. Correct.

[Nic Brough -Adaptavist-]

Ok, that proves that your process is not indexing the sub-tasks. So, where are you running this transition? It's not on the sub-task because that would index it

[Omprakash Thamsetty]

@Nic Brough [Adaptavist] I am opening the parent task and then creating the sub-task from there. The workflow post functions are placed in sub-task "Create" transition.

[Nic Brough -Adaptavist-]

Oh, hang on, I'd missed that - "create". There's a bug in the function that means it can't index fields on create. I think it's limited to system fields - could you check if you can replicate the problem with "frequency" (as that's a custom field, not system)

[Omprakash Thamsetty]

@Nic Brough [Adaptavist] . I reproduced the issue and then I searched with "Frequency" field then its showing the results. But not for assignee field. Is there a way to fix for system fields indexing for sub-task?

[Nic Brough -Adaptavist-]

Not that I know of. It's a bug in the JSU add-on from what I can see. I'd raise it at https://jsutil.atlassian.net/browse/JSUTIL

[Omprakash Thamsetty]

@Nic Brough [Adaptavist] Can I have the ticket number so that I will also add watcher to that? Thanks for the information and help on this

[Omprakash Thamsetty]

@Nic Brough [Adaptavist] Is the issue number JSUTIL-274 in JSUTIL ?

[Nic Brough -Adaptavist-]

Well spotted - I didn't have it bookmarked, and didn't look, but that is what I was thinking of. Sorry I didn't notice the "create" problem earlier!

[Omprakash Thamsetty]

We did work around on this. We added script workflow function from inline function and then running the sql command to convert the user-name from upper case to lower case. Here is the image and then script that we are using. Hope it may help others this work around until fix the bug.

workflowPostfun.jpg

//Import items for SQL Update Statement:
import com.atlassian.jira.ComponentManager
import groovy.sql.Sql
import java.sql.Connection
import org.ofbiz.core.entity.ConnectionFactory
import org.ofbiz.core.entity.DelegatorInterface
import com.atlassian.jira.event.issue.AbstractIssueEventListener
import com.atlassian.jira.event.issue.IssueEvent
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.ComponentManager
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.IssueManager
import com.atlassian.jira.util.ImportUtils
import com.atlassian.jira.issue.index.IssueIndexManager

ComponentManager componentManager = ComponentManager.getInstance()

//Create and run the SQL Update statement to change the assignee to Lower Case
delegator = (DelegatorInterface) componentManager.getComponentInstanceOfType(DelegatorInterface.class)
String helperName = delegator.getGroupHelperName("default");
def UpdateId = issue.getId()

//Make sure to change the schema as per JIRA db
def sqlStmt = """
    UPDATE [jiraschemaP].[jiraissue]
    SET [ASSIGNEE] = LOWER([ASSIGNEE])
    WHERE id = '""" + UpdateId + """';
"""
//sqlStmt.toString()
Connection conn = ConnectionFactory.getConnection(helperName);
Sql sql = new Sql(conn)
StringBuffer sb = new StringBuffer()
sql.execute(sqlStmt)

//Now run the re-index on this issue
    IssueIndexManager indexManager = ComponentManager.getInstance().getIndexManager()
    boolean wasIndexing = ImportUtils.isIndexIssues()
    ImportUtils.setIndexIssues(true)    
    IssueManager issueManager = ComponentManager.getInstance().getIssueManager()
    indexManager.reIndex(issueManager.getIssue(issue.id))
    ImportUtils.setIndexIssues(wasIndexing)