Limiting the selection of Date and Time if it is already selected in previous issues.

Question

Hi,

I have two Date and Time custom fields on create issue screen

1. From

2.To

Which i am using to select the period of time by the users

Requirement:

I want to restrict other users from selecting the same period of time if someone has already has selected it in.

Kindly help me out to achieve this with out use of any plugins, I guess we can have some java code in the description of a custom field.

Could any one please help me with similar java code to achieve this.

Thank You in Anticipation

Regards,

Ravinder Reddy.S

Kavi · Answer

Hi @Ravinder Reddy Singireddy Could you please let me know if you got any response/solution to restrict date/calendar field?

We are looking for options to restrict someone not to choose a past date and time.

Thanks.

Ravinder Reddy Singireddy · Answer

Hi Earl,

Thanks for the response.

I would like to make my requirement more clear, may be i did not provide enough information.

Its not the user's that I want to restrict i want to restrict the selection that is being done for my date time custom field.

I want something like if a user selects certain value(date time) then the script should fetch the custom field value's(date time) from database that were already entered on other issues and compare them with the present entered value.

The issue needs to be created with the value(date time) entered only if there is no such date and time selected previously else it should return a error.

I am trying to create some kind of booking system.

Regards,

Ravinder Reddy.S

Earl McCutcheon · Answer

Helo Ravinder,

Jira natively does not have the ability to restrict permissions at the field level to make a single field read only or only editable by a speciffic set of users the permissions to edit are set at the project level and a user an either can edit OR cannot edit the avaliable fields.  Also, this is not a feature that will be implemented in the future, as discussed in the following feature request that was closed as a Won't Fix, but goes into detail explaining the reasoning for why this choice was made in the status update in the issues description and the comments of the request:

* https://jira.atlassian.com/browse/JRASERVER-1330

However as discussed in the description the following workarounds are available:

Workarounds
Higher in the thread Erik S makes a comment about a workaround that may be useful for some users:
http://jira.atlassian.com/browse/JRA-1330?focusedCommentId=55032#action_55032
it is documented further here:
http://confluence.atlassian.com/pages/viewpage.action?pageId=149834
Third party commercial plugin:
https://plugins.atlassian.com/plugin/details/23216

There is also a recommendation for the tool Jjupin covered in this post:

* https://community.atlassian.com/t5/Jira-questions/How-do-I-prevent-a-field-from-being-edited-after-an-issue-has/qaq-p/123710

And a method using workflow properties discussed in the following post noting that this method will disable some functionality within the application such as inline editing form the applications view screen if used:

* https://community.atlassian.com/t5/Jira-questions/Set-particular-custom-field-read-only/qaq-p/296959

Regards,
Earl