How do we stop Agile from randomly editing screens?

Every now and then, our custom configuration versioning software detects changes made by what seems to me to be GreenHopper. These changes break already established order in which fields are appearing on the screen, and introduction of 'Epic Link' field usually makes no sense because the change is usually made on the screen specifically designed for tasks of the 'Epic' type, only (i.e. no other project screens are affected). Moreover, we're actively discouraging making changes without priorly creating a task in which they should be properly described, and we find such automatic out-of-the-blue changes rather interfering.


So, how can we stop Agile from messing with already configured screens?

2 answers

0 votes
Steven Behnke Community Champion Dec 17, 2015

I think scheme config changes only happen when users create projects using templates. Is it possible to find the spot that I can reproduce this?

Well, it actually is as simple as: /secure/RapidStart.jspa → Scrum → Board from an existing project → pick a project; any screen associated with a project via screen schemes get modified. I can even show the traceback of where this actually happens (this was generated with the help of an SQL trigger that prohibits any activity on {{fieldscreenlayoutitem}} table): {noformat} at at at com.atlassian.jira.issue.fields.screen.DefaultFieldScreenStore.updateFieldScreenLayoutItem( at com.atlassian.jira.issue.fields.screen.CachingFieldScreenStore.updateFieldScreenLayoutItem( at com.atlassian.jira.issue.fields.screen.DefaultFieldScreenManager.updateFieldScreenLayoutItem( at at at com.atlassian.jira.issue.fields.screen.FieldScreenTabImpl.moveFieldScreenLayoutItemToPosition( at com.atlassian.greenhopper.customfield.CustomFieldScreenServiceImpl.addFieldToScreen( at com.atlassian.greenhopper.customfield.CustomFieldScreenServiceImpl.addFieldToScreens( at com.atlassian.greenhopper.customfield.CustomFieldScreenServiceImpl.addFieldForIssueOperations( at com.atlassian.greenhopper.customfield.CustomFieldConfigurationRestorerImpl.addFieldToScreens( at com.atlassian.greenhopper.customfield.CustomFieldConfigurationRestorerImpl.addCustomFieldsToScreens( at com.atlassian.greenhopper.customfield.CustomFieldConfigurationRestorerImpl.ensureFieldsAreCorrectlyConfigured( at com.atlassian.greenhopper.web.rapid.view.RapidViewHelper.createRapidViewWithProjects( at com.atlassian.greenhopper.web.rapid.view.RapidViewHelper.createRapidViewWithProjects( at com.atlassian.greenhopper.web.rapid.view.RapidViewHelper.createRapidViewForPreset( at com.atlassian.greenhopper.web.rapid.view.RapidViewResource$ at com.atlassian.greenhopper.web.rapid.view.RapidViewResource$ at com.atlassian.greenhopper.web.util.RestCall.response( at com.atlassian.greenhopper.web.AbstractResource.createResponse( at com.atlassian.greenhopper.web.AbstractResource.response( at com.atlassian.greenhopper.web.rapid.view.RapidViewResource.setupView( at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke( at … {noformat}

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,904 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