Multiple Start and End Time fields confusing users and complicating Change Calendar

[John Block]

I have multiple fields I am using to display the Start and End Times of Change Requests because how the Change Calendar works.

Fields:

"Planned Start", "Planned End", "Maintenance Start Time", and "MaintenanceEndTime"

Currently the Change Calendar only works when the Planned Start and Planned End fields are populated. This is shown to be a requirement of the Calendar.

The issue I am experiencing is that the Maintenance Start Time and MaintenanceEndTime fields cannot be removed from the Request Form due to the fields being created by Jira Service Management.

I've gotten around this for the time-being by copying the values from the Maintenance Start and End fields to the Planned Start and Planned End fields. This requires multiple automations and occasionally items will display on the Calendar incorrectly depending on how the end users update the fields after initial population of them.

I would like to only use the Planned Start and Planned End fields so I can clear out my automations and not have start and end times populated in multiple places. This will clean up the number of automations I have on this Project and will simplify the process. My blocker is Jira not allowing me to remove the Maintenance Start Time and MaintenanceEndTime fields. I was looking to see if anyone has run into a similar issue.

[Beylem Cindoğlu · Accepted solution]

Hello Community!

I'm currently working on enhancing our change management processes and am focusing specifically on leveraging Jira Service Management's (JSM) change management features, including the change calendar.

I’m looking to connect with fellow users who have experience with JSM's change management capabilities. If you are currently using the change management feature, especially the calendar, I would love to hear about your experiences, challenges, and best practices.

Your insights will be invaluable as I work to optimize our approach and ensure we're utilizing these tools to their fullest potential.

Thank you in advance for your help and looking forward to engaging with this knowledgeable community!

What’s involved in the research:

• Sessions are 1 hour and conducted over video-conference, so you can participate from anywhere around the globe.

• During the research, we'll start with a general chat to get to know you, understand your workflow in regards to change management.

• As a token of our appreciation, you'll receive an e-gift card worth $100 USD within 5 business days of completing your session.

Interested in taking part? Follow this link to fill in a few more details so we can make sure you’re a good fit.

If you have any other questions at all, feel free to reply to this post or email me directly on bcindoglu@atlassian. We look forward to meeting you!

Cheers,

Beylem Cindoğlu

JSM Design Team

[Tomislav Tobijas _Koios_ · Accepted solution]

Hi @John Block ,

Question regarding those two fields - did you use any specific templates when creating a project? I checked one of our instances but there are no "Maintenance Start Time", and "Maintenance End Time" fields (although this is a bit older site so not sure if it's up to that).

I've also checked JAC about this issue, but cannot seem to find any open tickets related to it.

If nothing, I would suggest reaching out to the support team as they can access your instance (if you let them) and debug this further; or potentially open a new bug/suggestion on JAC.

Cheers,
Tom

[John Block]

@Tomislav Tobijas _Koios_ , 

I had cloned another project to create this new one. I imagine that is where the Maintenance Start and Maintenance End custom fields came from. 

I will look into support and provide any updates here. 

[Tomislav Tobijas _Koios_]

Might be these are then custom fields.

In any case please share what you've learned in case maybe that will help other community members :)

[John Block]

After further review, we found that the fields being set as "Required" prevented them from being removed from the form view. Once set to "Optional" I was able to replace them with the preferred Planned Start and Planned End fields.

[Tomislav Tobijas _Koios_]

@John Block glad to hear you've managed to sort this out! Thanks for sharing the resolution!