Explicit Policies help define clear guidelines and rules for each stage of the workflow to ensure smooth progress and prevent bottlenecks. Here’s a suggested template with sections for each typical column in a Kanban board: Remember that Explicit Policies should be clear, concise, and easy to understand. They should also be open to improvement based…
Read MoreIs there a way to change the “Resolution Date” in Jira?
First you must read this trick: Example of script field in Jira to know the Closing date After this, try to: Just export a CSV of the issues you need to update. Add a “resolved date” column, populate dates, then import into JIRA as Admin via External System Import. Note1: If you CSV contain more…
Read MoreExample of script field in Jira to know the Closing date
Sometimes we need to know the “real” closing date of tickets, for different reasons: workflows with bad config (Resolve Issue screen missing in final statuses…), two Resolve Issue screens in Resolved and Closed statuses, etc. And, as always, we have a trick using the plugin Scriptrunner! It’s very simple, just create a Scripted custom field…
Read MoreHow to create a new subtask when other subtask is done or resolved in Jira
Sometimes we need to raise new subtasks when other subtasks are finished. In this example we explain how we can do this in Jira using the famous plugin Adaptavist Scriptruner. The trigger of the action is the “transition”: when someone moves a subtask from one status to another. In this case, from “IN PROGRESS” to…
Read MoreAtlassian 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 MoreHow to restrict resolution options in JIRA
Very easy! Edit the Workflow transition to “CLOSED“ Click on “Properties“ Add this pair “key – value” jira.field.resolution.include = id_resolution_1, id_resolution_1023, .. That’s all!
Read More