Advanced Roadmaps - How to assign a Shared Team to a Subtask

[Pierre Leroux]

At BKOM Studios we usually have groups of resources of a single DISCIPLINE (frontend, backend, UI Design...) but following Agile methodology we also have SCRUM teams, which are multi-disciplinary teams. Therefore, a single person can be part of a DISCIPLINE team (vertical, skill-based and shared among projects) and be part of a SCRUM team (horizontal, feature oriented, linked to a specific project). Way before starting sprints, we tend to assign Stories to SCRUM teams, and anticipated sub-tasks to DISCIPLINES, through JIRA's components, so that we can anticipate somehow the needs for each resources. But we would like to anticipate better the work to come in order to maximize the planning. Before starting sprints, we would like to assign sub-tasks to specific DISCIPLINE team, so that we can forecast better the workload on each of the DISCIPLINES over time. At the moment, it seems Advance Roadmaps doesn't permit sub-task assignment to Teams. Is that confirmed of did we miss something? If it's confirmed, do we know the reason of this limitation? Is there anyone having a workaround to this limitation? 

[Mark Markov · Accepted solution]

Hello @zaharovvv_suek_ru

You can use ScriptRunner Behaviours for this

Add-ons -> Behaviours - Add

Add mapping to your project and issue types

Fields -> Add -> Epic Link 

Add server-side script on that field

if (getActionName() != "Create") {
    getFieldById(getFieldChanged()).setHidden(true)
}

[Mark Markov]

It will be looks like this

[zaharovvv_suek_ru]

@Mark Markov Thank you very much for your reply!

I've forgot to say that this should applied just for issues which have "Epic Link". 

I've tried to use the following code: 

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.Issue

def customFieldManager = ComponentAccessor.getCustomFieldManager();
def epicLink = customFieldManager.getCustomFieldObjectByName('Epic Link');
def epic = issue.getCustomFieldValue(epicLink);

if (getActionName() != "Create" && epic) {
   getFieldById(getFieldChanged()).setHidden(true)
}

 However, I see the error: The variable [issue] is undeclared.

How can I check whether there is an 'Epic Link' ?

Thanks in advance.

[Mark Markov]

Because behaviours doesnt have issue variable.

Try to use 

def epic = underlyingIssue.getCustomFieldValue(epicLink);

 instead

[zaharovvv_suek_ru]

@Mark Markov

Thank you very, very, very much! It worls like a charm!

The full code looks like this:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.Issue

def customFieldManager = ComponentAccessor.getCustomFieldManager();
def epicLink = customFieldManager.getCustomFieldObjectByName('Epic Link');
def epic = underlyingIssue.getCustomFieldValue(epicLink);

if (getActionName() != "Create" && epic) {
    getFieldById(getFieldChanged()).setHidden(true)
}

[Mark Markov]

You re welcome :)

[Tarun Sapra]

Hello @zaharovvv_suek_ru

You have to customize the screen scheme definition. Basically make sure that "Epic link" field is available on create and view screen and not present on edit screen.

Please read the docs here as to how you can create screen scheme and map it with issueType

https://confluence.atlassian.com/adminjiraserver/associating-a-screen-with-an-issue-operation-938847289.html

[zaharovvv_suek_ru]

@Tarun Sapra 

Thanks for your reply! I'm sorry I've forgot to say that this should applied just for issues which have "Epic Link".  Thanks in advance.

[Tarun Sapra]

Ok, then please go with the answer provided by @Mark Markov

[Grigory Salnikov]

Hi!

Yes, it is possible. You should edit the Screen Scheme associated with the project to make 2 different screens for edit and view.

[Grigory Salnikov]

This article should help to understand this operation.

[zaharovvv_suek_ru]

@Grigory Salnikov

Thanks for your reply! I'm sorry I've forgot to say that this should applied just for issues which have "Epic Link".  Thanks in advance.

[Grigory Salnikov]

Ok. I see. You're welcome!