How to avoid to log work in Jira Epics

Disable “Log work” on Epics in Jira is possible and it’s very easy, here the instructions: Create a Workflow only for the Epic In all statuses/steps of the workflow add this property: jira.permission.work.denied  Assign the Workflow to the Workflow Scheme of the target project and assign to the issue type Epic ( Remember to publish…

Read More

How to modify “Original Estimate” in JIRA after log work in the Issue

To make editable the field “Original Estimate” after log work in the Issue, you must change the “Legacy Mode” in the “Time Tracking” configuration. About ‘Legacy Mode’ If Legacy Mode is disabled, your users will be able to change the Original Estimate value irrespective of any work being logged on an issue. Legacy Mode is disabled by default…

Read More

Atlassian Crowd LDAP problems and downtimes?… see this post

After the upgrading of Crowd, our servers experimented a new problem… sometimes Crowd becomes “stuck” (also JIRA & Confluence because the SSO) and the log of Crowd show errors in the LDAP connection… but not always… two times a week.. etc. Examples of errors in the log: Caused by: com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException…

Read More