Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Flexible Datetime Fields for Ticket and Issue Management

Alfredo Ramirez
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 2, 2024

Hi all! I'm working with my team to create a comprehensive timeline of an issue and I'm exploring if there is a way to add flexibility to the date and calendar field functionality for our tickets.

Currently, our tickets correspond to an individual case where we track four specific fields related to the ticket in custom fields. In our case, these are: X Start Date, X End Date, Last Day to Ask About X, and Last Day to Submit for X.

There are about a dozen additional date or datetime fields that broadly cover our issues. However, they are not exhaustive and only address 80% of our cases. My team wants a dynamic option that allows us to create a new datetime field when a ticket requires it. In this case, a ticket might have 3 or 30 datetime fields with three items required to report on the information: (1) Name of Datetime Field, (2) Datetime component, and (3) Required (Yes or No).

My question to the community: is it possible to create this structure so I can have a dynamic number of datetime fields for each issue, or am I limited to the datetime fields I create.

0 answers

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events