Didit custom field best practices

Screens

We recommend that you keep the Didit custom fields hidden from the create and edit screen. These fields store data which is automatically populated based on checklist inputs and changes, so editing this could result in faulty data and mess with some of your automation rules. If you can tolerate only seeing the data in these fields once in a while, you could choose create a filter in Jira and add these fields to your filter’s column layout. If you must see these fields on Jira screens regularly, we suggest adding them to only the “view” screen in your issue type screen scheme.

Field configurations

Under any circumstance, don’t make these fields required in your field configuration. These fields will be empty by default and populated once work on the checklist begins.

Workflows

We list out some of the possibilities within workflow functions on our workflows page. If the use case you are looking for is not on this page, please consult us before implementing it.

Notifications

This isn’t so much a best practices but rather a quick note that we have suppressed all notifications related to the Didit custom fields. You can still trigger automation rules based on these updates.

Link to this page: https://seibert.biz/diditcustomfieldbest