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

Kyung Hwan Kim July 10, 2013
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

0 votes
Boris Georgiev _Appfire_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 10, 2013

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