What type of issues if you modify the schema changes to the underlying schema please?

The project's issue type scheme has changed. However, the issue of a different project type schema as the default schema is changed. Why is that? FieldConfigScheme configScheme = getConfigScheme(); List projectsList; List associatedProjects = configScheme.getAssociatedProjects(); if (associatedProjects != null && !associatedProjects.isEmpty()){ projectsList = new ArrayList(associatedProjects); }else{ projectsList = new ArrayList(1); } projectsList.add(getProject()); Long[] projectIds = GenericValueUtils.transformToLongIds(projectsList); setProjects(projectIds); List contexts = CustomFieldUtils.buildJiraIssueContexts(false, null, getProjects(), treeManager); configScheme = configSchemeManager.updateFieldConfigScheme(configScheme, contexts, getConfigurableField()); fieldManager.refresh();

1 answer

Can you give more details of what exactly you're trying to achieve with this code ? I think that FieldConfigScheme has noting to do with issue type schemes. FieldConfigScheme is actually a custom field context,

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,919 views 19 22
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you