nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Built in scripts from 'Generate Events' wont trigger Insight Read Only field to update

Steve Letch

Hi all

I'm implementing an Insight Read only field into my screens. Insight read only fields are triggered to fill on Issue Created and Issue Updated. the field fills fine when you use native Jira functions such as create an issue, inline edit a field or bulk change something else about issues.

I wanted to get the field populated for our old issues, however the built in script to 'Generate Events', Issue Updated and Issue Created don't trigger the field to fill. I've even tried a script in the script console to bulk update a dummy field attached to issues to see if that would trigger it but sadly not.

The only thing this Insight field seems to respond to is native Jira functionality, at least with the methods I've tried.

Does an additional class need to be added to a custom event or something

Thanks

Accepted answers

PD Sheehan

I haven't tried that... but I think you could run a script that runs a JQL to return an issue where the RO Insight field is missing, then just use issue.setCustomFieldValue(objectKey)

I suspect that's what insight does when it detects the issue updated, issue created, and possibly also the issue assigned events.

If you've never done groovy scripting for jira (like with scriptrunner) it would look something like this:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.jql.parser.JqlQueryParser
import com.atlassian.jira.issue.search.SearchProvider
import com.atlassian.jira.web.bean.PagerFilter
import com.atlassian.jira.issue.search.SearchQuery
import com.atlassian.jira.util.ImportUtils
import com.atlassian.jira.event.type.EventDispatchOption
import com.atlassian.jira.issue.index.IssueIndexingService

def issueManager = ComponentAccessor.issueManager 
def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser)
def searchProvider = ComponentAccessor.getComponent(SearchProvider)
def currentUser = ComponentAccessor.jiraAuthenticationContext.loggedInUser

def someObjectkeyToSet = 'ABC-123'
def jql =""" Project = PJCT and "Insight ReaOnly Field" is empty """

def query = jqlQueryParser.parseQuery(jql.toString())
def searchQuery = SearchQuery.create(query,currentUser)
def results = searchProvider.search(searchQuery, PagerFilter.newPageAlignedFilter(0,1))

results.results.document.each{ 
    def issue = issueManager.getIssueObject(it.getValues('issue_id').first() as Long)
    def customField = ComponentAccessor.customFieldManager.getCustomFieldObjectsByName("nsight ReaOnly Field")[0]
    //apply the value
    issue.setCustomFieldValue(customField, someObjectkeyToSet)

    //Store the issue
    issueManager.updateIssue(currentUser, issue, EventDispatchOption.DO_NOT_DISPATCH, false)

    //update the JIRA index
    boolean wasIndexing = ImportUtils.isIndexIssues()
    ImportUtils.setIndexIssues(true)
    ComponentAccessor.getComponent(IssueIndexingService.class).reIndex(issue)
    ImportUtils.setIndexIssues(wasIndexing)
}

All comments

PD Sheehan

I haven't tried that... but I think you could run a script that runs a JQL to return an issue where the RO Insight field is missing, then just use issue.setCustomFieldValue(objectKey)

I suspect that's what insight does when it detects the issue updated, issue created, and possibly also the issue assigned events.

If you've never done groovy scripting for jira (like with scriptrunner) it would look something like this:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.jql.parser.JqlQueryParser
import com.atlassian.jira.issue.search.SearchProvider
import com.atlassian.jira.web.bean.PagerFilter
import com.atlassian.jira.issue.search.SearchQuery
import com.atlassian.jira.util.ImportUtils
import com.atlassian.jira.event.type.EventDispatchOption
import com.atlassian.jira.issue.index.IssueIndexingService

def issueManager = ComponentAccessor.issueManager 
def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser)
def searchProvider = ComponentAccessor.getComponent(SearchProvider)
def currentUser = ComponentAccessor.jiraAuthenticationContext.loggedInUser

def someObjectkeyToSet = 'ABC-123'
def jql =""" Project = PJCT and "Insight ReaOnly Field" is empty """

def query = jqlQueryParser.parseQuery(jql.toString())
def searchQuery = SearchQuery.create(query,currentUser)
def results = searchProvider.search(searchQuery, PagerFilter.newPageAlignedFilter(0,1))

results.results.document.each{ 
    def issue = issueManager.getIssueObject(it.getValues('issue_id').first() as Long)
    def customField = ComponentAccessor.customFieldManager.getCustomFieldObjectsByName("nsight ReaOnly Field")[0]
    //apply the value
    issue.setCustomFieldValue(customField, someObjectkeyToSet)

    //Store the issue
    issueManager.updateIssue(currentUser, issue, EventDispatchOption.DO_NOT_DISPATCH, false)

    //update the JIRA index
    boolean wasIndexing = ImportUtils.isIndexIssues()
    ImportUtils.setIndexIssues(true)
    ComponentAccessor.getComponent(IssueIndexingService.class).reIndex(issue)
    ImportUtils.setIndexIssues(wasIndexing)
}

Steve Letch

Will give it a go tomorrow and let you know, thanks

Steve Letch

Hi @PD Sheehan

The part of the script where it tries to select a specific key, I need it to just do it's normal job whereby the content of the field is filled depending on the reporter.

My insight field is configured as follows:

Filter Scope (IQL)

objectType = Users

Filter Assign Scope (IQL)

User = currentReporter()

PD Sheehan

You can use the IQLFacade to find the object

def iqlFacade = ComponentAccessor.getOSGiComponentInstanceOfType(IQLFacade)
def iqlResults = iqlFacade.findObject("objectType = Users and User = $issue.reporter.name"
def objectKeyToSet
if(iqlResults){
   objectKeyToSet = iqlResults.first().objectKey
}

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

adaptavist

insight