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 vote
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 com.atlassian.jira.ofbiz.DefaultOfBizDelegator.store(DefaultOfBizDelegator.java:377) at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.store(WrappingOfBizDelegator.java:212) at com.atlassian.jira.issue.fields.screen.DefaultFieldScreenStore.updateFieldScreenLayoutItem(DefaultFieldScreenStore.java:130) at com.atlassian.jira.issue.fields.screen.CachingFieldScreenStore.updateFieldScreenLayoutItem(CachingFieldScreenStore.java:162) at com.atlassian.jira.issue.fields.screen.DefaultFieldScreenManager.updateFieldScreenLayoutItem(DefaultFieldScreenManager.java:106) at com.atlassian.jira.issue.fields.screen.FieldScreenLayoutItemImpl.store(FieldScreenLayoutItemImpl.java:80) at com.atlassian.jira.issue.fields.screen.FieldScreenTabImpl.store(FieldScreenTabImpl.java:102) at com.atlassian.jira.issue.fields.screen.FieldScreenTabImpl.moveFieldScreenLayoutItemToPosition(FieldScreenTabImpl.java:235) at com.atlassian.greenhopper.customfield.CustomFieldScreenServiceImpl.addFieldToScreen(CustomFieldScreenServiceImpl.java:52) at com.atlassian.greenhopper.customfield.CustomFieldScreenServiceImpl.addFieldToScreens(CustomFieldScreenServiceImpl.java:99) at com.atlassian.greenhopper.customfield.CustomFieldScreenServiceImpl.addFieldForIssueOperations(CustomFieldScreenServiceImpl.java:92) at com.atlassian.greenhopper.customfield.CustomFieldConfigurationRestorerImpl.addFieldToScreens(CustomFieldConfigurationRestorerImpl.java:111) at com.atlassian.greenhopper.customfield.CustomFieldConfigurationRestorerImpl.addCustomFieldsToScreens(CustomFieldConfigurationRestorerImpl.java:87) at com.atlassian.greenhopper.customfield.CustomFieldConfigurationRestorerImpl.ensureFieldsAreCorrectlyConfigured(CustomFieldConfigurationRestorerImpl.java:62) at com.atlassian.greenhopper.web.rapid.view.RapidViewHelper.createRapidViewWithProjects(RapidViewHelper.java:375) at com.atlassian.greenhopper.web.rapid.view.RapidViewHelper.createRapidViewWithProjects(RapidViewHelper.java:142) at com.atlassian.greenhopper.web.rapid.view.RapidViewHelper.createRapidViewForPreset(RapidViewHelper.java:111) at com.atlassian.greenhopper.web.rapid.view.RapidViewResource$2.call(RapidViewResource.java:63) at com.atlassian.greenhopper.web.rapid.view.RapidViewResource$2.call(RapidViewResource.java:59) at com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:42) at com.atlassian.greenhopper.web.AbstractResource.createResponse(AbstractResource.java:115) at com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:96) at com.atlassian.greenhopper.web.rapid.view.RapidViewResource.setupView(RapidViewResource.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at … {noformat}

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Posted 13 hours ago in Jira

We want to know what Jira Service Desk apps you're using!

Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...

36 views 0 5
Join discussion

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