• 54
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      I have users selecting a need by date for equpiment and they can currently choose a date that has already passed. We would like to have an option to disable dates before the current date.

            [JSDCLOUD-545] Disable dates in the past in customer portal

            Users can artificially escalate an issue by selecting a date in the past.  At the very least an option to prevent past date is needed.  

            Shawn Jamison added a comment - Users can artificially escalate an issue by selecting a date in the past.  At the very least an option to prevent past date is needed.  

            Saurabh Kapoor added a comment - https://getsupport.atlassian.com/browse/JST-892508

            Team Atlassian, has this been fixed yet?

            This is impacting some automation rules that are time-based, and due to miss-selecting a past date could result in failed automation rule calculations. 

            Thanks,

            Sherif

            Sherif Abdellatif added a comment - Team Atlassian, has this been fixed yet? This is impacting some automation rules that are time-based, and due to miss-selecting a past date could result in failed automation rule calculations.  Thanks, Sherif

            In my portal my customers are also allowed to select a date in the past even though I have a validator that says they can't.  Please update the customer portal so a client can't chose a date in the past.

            Thanks!

            Katherine Stevens added a comment - In my portal my customers are also allowed to select a date in the past even though I have a validator that says they can't.  Please update the customer portal so a client can't chose a date in the past. Thanks!

            Team Atlassian, this is another one looks like more basics and simple fix. appreciate if this can be expedited and fixed ASAP.

            Is there any workaround for the same?

            Thanks

            Brijesh

            Brijesh Pathak added a comment - Team Atlassian, this is another one looks like more basics and simple fix. appreciate if this can be expedited and fixed ASAP. Is there any workaround for the same? Thanks Brijesh

            Why not allow more validation? Like if I have a "when do you want this delivered" and know that I use 2 day shipping, I want to block today's date +2 days.

            steven.baron added a comment - Why not allow more validation? Like if I have a "when do you want this delivered" and know that I use 2 day shipping, I want to block today's date +2 days.

            I'd really like to see this solved for! We don't want to other our agents to have to spend time going back and forth with a requester when they mistakenly enter a date in the past.

            Of course, there are scenarios where we want the users to enter dates in the past, so we will want this to be configurable. Using validators in the workflow works for me! But if you have a different solution coming, totally open to that.

            Thanks!

            Heather Rommel [HyperVelocity] added a comment - I'd really like to see this solved for! We don't want to other our agents to have to spend time going back and forth with a requester when they mistakenly enter a date in the past. Of course, there are scenarios where we want the users to enter dates in the past, so we will want this to be configurable. Using validators in the workflow works for me! But if you have a different solution coming, totally open to that. Thanks!

              Unassigned Unassigned
              6a8d34554120 Katie O'Hern
              Votes:
              129 Vote for this issue
              Watchers:
              46 Start watching this issue

                Created:
                Updated: