Hello!

I just updated to the newest version and now it works also with 6.1.2.

Thank you, Roland

Hi d8cbcac22823, some time has passed but there is fixed version of the calendar for your problem. Please, let me know if this solves your issue.

hello!

i just created a new date/time field in our testing system an associated it with a field configration scheme.

• Good news: it works fine, i can select it via the plugin and it shows the right date in the widget
• Bad news: That doesn't help me with our existing fields as they are widely used in a lot of Jira Issues and i can't create a new field wich replaces the existing one. and ist still works wih plugin version 6.0.2 

d8cbcac22823, I'm really confused right now so I'd like to ask 2 more questions:

1. Have You tried to do this using sys admin account or any other with all privileges?
2. Try to create new global date custom field without any association and try to select it in calendar gadget. Does the problem still exist?

Thanks in advance for Your answers.

hi!

thank you, but i'm sorry to tell you, that, after updating the version to 6.1.1 in our testing system, the problem still persists.

• when i try to change the widget date to display to our custom field,
• it switches back to "due date"

d8cbcac22823, 6.1.1 is released You can try it.

to be honest i don't understand your last question. what do you mean with user has or has no acces to any project. maybe you can add a screenshot.

as of now, every user has access to edit the custom date field, when he creates or edits a Jira Issue with the specifix issue type. and there are no differences.

the only difference is:

• using plugin version 6.0.2 with Jira version 9.8.1: calender widget works fine
• using plugin version 6.1.0 with Jira version 9.8.1: calender widget works fine - computer says no

d8cbcac22823, so context is global. Last question: on the instance, is there any existing project to which user has access? or user has no access to any project / there's no project on the instance?

hi! 

to 1: 

• it is not project specific but specific to a custom issue type, whicht belongs to a screen them, that nearly every project is assigned to

to 2 and 3:

• everybody who uses this specific issue type can edit these custom fields
• the context is global (for all projects)

as i mentioned before, is everything working fine, when we use the plugin version 6.0.2 as mentioned in the fix-version of this Jira issue. The problem occurs only again, when we update to the latest version 6.1.0.

d8cbcac22823, thanks again for Your answers I have 3 more questions:

1. Is this custom field set as global or available only for selected projects?
2. if this custom field is set as global - does user have access to any existing project?
3. If this custom field is set as available only for selected projects - does user have access to any associated project?