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; } } }

Determine is screen opened is an Edit screen

Aleksandr Serebriakov

Messing with Behaviors....

What I am trying to do is to determine is a currently opened screen is an Edit screen.
As I see it, I have to get a current screen scheme and screen id assigned as an Edit screen in it.
Then I have to get a currently opened screen id and compare them.

Googled it a lot ad tried dozens of code examples, but keep bumping on basically the same kind of dead ends. Either I cant get current issue id (what is needed in one kind of code), or I get something like this:


groovy.lang.MissingPropertyException: No such property: IssueOperations for class:

The Goal is to determine is opened screen is an Edit screen. Maybe the is an other way to do that.

Accepted answers

Alexey Matveev

Hello,

The code would be like this

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.operation.IssueOperations

def issue = ComponentAccessor.getIssueManager().getIssueByCurrentKey("issuekey");
def screen = ComponentAccessor.getIssueTypeScreenSchemeManager().getFieldScreenScheme(issue).getFieldScreenSchemeItem(IssueOperations.EDIT_ISSUE_OPERATION )

log.error("eidt screen id" + screen.getId())

import com.atlassian.jira.component.ComponentAccessor
def issue = ComponentAccessor.getIssueManager().getIssueByCurrentKey("issuekey");
def screen = ComponentAccessor.getIssueTypeScreenSchemeManager().getFieldScreenScheme(issue).getFieldScreenSchemeItems().find {
 it.getIssueOperationName() == "admin.issue.operations.edit";
 }

log.error("eidt screen id" + screen.getId())

All comments

Aleksandr Serebriakov

So I managed to get Screen scheme

import com.atlassian.jira.component.ComponentAccessor

def scrscheme = ComponentAccessor.getIssueTypeScreenSchemeManager()getFieldScreenScheme(getUnderlyingIssue())

Now I have to get Operation Screen. Something like:

scrscheme.getFieldScreen(IssueOperation issueOperation)

But how can I specify, for example EDIT screen?

IssueOperation issueOperation

Alexey Matveev

Hello,

The code would be like this

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.operation.IssueOperations

def issue = ComponentAccessor.getIssueManager().getIssueByCurrentKey("issuekey");
def screen = ComponentAccessor.getIssueTypeScreenSchemeManager().getFieldScreenScheme(issue).getFieldScreenSchemeItem(IssueOperations.EDIT_ISSUE_OPERATION )

log.error("eidt screen id" + screen.getId())

import com.atlassian.jira.component.ComponentAccessor
def issue = ComponentAccessor.getIssueManager().getIssueByCurrentKey("issuekey");
def screen = ComponentAccessor.getIssueTypeScreenSchemeManager().getFieldScreenScheme(issue).getFieldScreenSchemeItems().find {
 it.getIssueOperationName() == "admin.issue.operations.edit";
 }

log.error("eidt screen id" + screen.getId())

Aleksandr Serebriakov

Hello Alexey,

Once again you are helping me out

The first code doesn't work in my situation because using code in the Behaviors the last one could not import "...operation.IssueOperations", so IssueOperations.EDIT_ISSUE_OPERATION can't be used:

groovy.lang.MissingPropertyException: No such property: IssueOperations for class: Script1

The second one with a bit of modification does what I need. In situation with Behaviors, to get an issue object/key we have to use:

def issueId = formContents["id"]
def issueOBJ = ComponentAccessor.getIssueManager().getIssueObject(issueId as Long)

// or

def issueOBJ = getUnderlyingIssue()

Lyrical digression...
I thought that if I'll get an IssueOperationName it would be equivalent to "IssueOperations.EDIT_ISSUE_OPERATION", and if I'll put it into getFieldScreenSchemeItem() I would get what I want. So I started to play with loops trying to fetch info i need.

def VAR_1 = scrscheme_1.getFieldScreenSchemeItems()
VAR_1.each {
 log.debug (" ")
 log.debug (" IT " +it)
 if(it.getIssueOperation()){
 log.debug (" OPERATION ID " +it.getIssueOperation().getId())
 log.debug (" OPERATION KEY " +it.getIssueOperation().getNameKey())
 log.debug (" OPERATION DEC " +it.getIssueOperation().getDescriptionKey())
 log.debug (" OPERATION NAME " +it.getIssueOperationName())
 }
 }

I was wrong.

But it gave me a thought that from that loop I сan get what I need by taking an IssueOperation with the name I need ("admin.issue.operations.edit").
I was close Thank you for saving my time

Alexey Matveev

You are welcome

Aleksandr Serebriakov

I've just understood, that this code:

def screen = ComponentAccessor.getIssueTypeScreenSchemeManager().getFieldScreenScheme(issue).getFieldScreenSchemeItems().find {
 it.getIssueOperationName() == "admin.issue.operations.edit";
 }

returns an "Item" (...getFieldScreenSchemeItems().find...)

and

screen.getId()

returns an ID of that item.
So to get a Screen ID we need to use:

screen.getFieldScreenId()

Aleksandr Serebriakov

DUPLICATE OF THIS COMMENT

Aleksandr Serebriakov

DUPLICATE OF THIS COMMENT

Alexey Matveev

What Jira version do you use?

Aleksandr Serebriakov

6.2.4

Alexey Matveev

This is strange. I tested my code in a behavour but my version is 7.2.3

And I had a look in the Api reference this class is available in your Jira version