✑ Join
✑ Leave
Both issue types share a field configuration, screens and the workflow.
You currently use the Due Date system field to indicate when someone actually joins or leaves.
New HR staff members complain that using the Due Date field is not very intuitive.
How can you help your HR team?
A.
✑ Create individual Join Date and Leave Date custom fields to replace the Due Date field.
✑ Create separate screens for each issue operation and issue type.
✑ Delete the Due Date field.
B.
✑ Rename the Due Date field to Join Date and create a separate Leave Date custom field.
✑ Create new screens for the Leave issue type and replace the Due Date field with the newly created field.
✑ Migrate existing field values to the new Leave Date field.
C.
✑ Create individual field contexts for each issue type.
✑ Label the Due Date field as Join Date and Leave Date in their respective contexts.
✑ Associate each context with its matching issue type.
D.
Create individual Join Date and Leave Date custom fields to replace the Due Date field.
✑ Appropriately migrate existing data from the Due Date field to the new custom fields.
✑ Remove the Due Date field from all project screens.
- Your Hr Project 1 (116 Bytes) Viewed 50 times