-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3.10.2
-
3
-
Severity 3 - Minor
-
1
-
Workflow validators result in error when using name.
The behaviour is shown in the attached pictures.
- blocks
-
-
- Closed
-
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-5781] Workflow validators result in error when using name
I really like Jira, but it is very disappointing that bugs are just left open for more than 2 years, nearly 2,5 years now! If it would be something minor that never was available anyways, but a working validator function (with code already using that) was broken with other updates in 2018 and no one seems to care... Please fix it!
Still valid in Jira. 8.5.2 / SD 4.5.2, please update that! Bug report is from 04/2018!
This is open for nearly 1 year now! Please fix it...
Waiting for the fix, any updates when that will be addressed? Thanks!
Could you please fix the issue with a higher priority? Thanks in advance!
Thanks, Eric. Reposting my comment so images show.
There seems to be a regression of a worser kind in Service Desk 3.10.2 (and possibly other versions).
If your validator just throws a plain old exception with no field specified, you get a super generic error in the service desk portal that doesn't contain your custom message:
throw new InvalidInputException("Summary is incorrect")
If you do go to the trouble of specifying a field, you get the same generic exception plus your custom message (with no indication of the field):
throw new InvalidInputException(com.atlassian.jira.issue.IssueFieldConstants.COMPONENTS, "Summary is incorrect")
In the normal Jira view, you get errors like you would expect, indicating which field is broken and supplying your custom error message to the user.
This is from JSDSERVER-3592
There seems to be a regression of a worser kind in 3.10.2 (and possibly other versions).
So, if your validator just throws a plain old exception with no field specified, you get a super generic error in the service desk portal that doesn't contain your custom message:
throw new InvalidInputException("Summary is incorrect")
If you do go to the trouble of specifying a field, you get the same generic exception plus your custom message (with no indication of the field):
throw new InvalidInputException(com.atlassian.jira.issue.IssueFieldConstants.COMPONENTS, "Summary is incorrect")
Bug is open for over 3 years now... I thought Atlassian would care more for the technical quality in detail, but the times are changing obviously.