[SRJIRA3783] Behaviours SetRequired Method For Tempo Account And

[srjira-3783] behaviours - setrequired method for tempo account and teams field allows you to submit the value none created: 09/sep/19 update

[SRJIRA-3783] Behaviours - setRequired method for Tempo Account and
Teams Field allows you to submit the value None Created: 09/Sep/19
Updated: 17/May/21 Resolved: 05/Nov/20
Status:
Done
Project:
SR for Jira - Development
Component/s:
Behaviours
Affects Version/s:
5.5.9.1-jira8
Fix Version/s:
6.13.0
Type:
Bug
Priority:
Low
Reporter:
Matthew Clark
Assignee:
Jamie Echlin
Resolution:
Done
Votes:
2
Labels:
None
Remaining Estimate:
Not Specified
Time Spent:
Not Specified
Original Estimate:
Not Specified
Issue Links:
Cause
Sprint:
SR4J Sprint 87, SR4J Sprint 88
Critical Points:
4.7
Description
Behaviours setRequired method treats the None value in the Tempo
Account field as a valid value and allows the submition of the issue.
This is because Tempo set the value to the string "-1" rather than
null or empty.
How to reproduce:
1. Install any Tempo plugin (e.g. Tempo Timesheets)
2. Add new Tempo Account, link it with any project
3. Add account field on creation screen of any issue type in that
project
4. Create new Behaviours, mappings for that project/issue type combo
mentioned earlier
5. Add Initialiser with this code
getFieldByName("Account").setRequired(true)
6. Try to Create issue - in dialog window, the Account field will have
a red star and will look like required, but if you select "None" for
Account field, the issue will still be created
Comments
Comment by Andre Dario Moreira Serrano [ 28/Sep/20 ]
Hi
I'm Andre Serrano, ScriptRunner Product Manager.
I'm currently looking at our bugs backlog and trying to understand
which ones are still impacting our users.
Having said that, are you still with this need?
Cheers
Comment by František Špaček [MoroSystems] [ 28/Sep/20 ]
Hi Andre,
the problem here lies mostly in Jira itself (or Confluence and their
connection). We tried to mitigate issue with Confluence unable to
create issue in Jira when there are any required fields in Jira. We
need Account field to be required for all users creating issue inside
Jira (we dont want to have unaccounted hours, thats pretty dangerous),
but when creating issues from Confluence (classic way of selecting
text and clicking Jira icon) won't let you create issue due to Account
field being required. So we wanted Account field to be set required
within Behaviours just for screens and be optional in Jira itself.
This way we are finally able to create issues from Confluence
maintaining requirement for all fields on screens thanks to
Behaviours.
It of course also applies to all other fields, but these we are able
to put as required only on create screens with Behaviours and they
work as intended, problem with Tempo is that selecting value "None" in
select results of value -1, which is not evaluated as empty field and
even if you set field required with behaviours, it lets you create
issue with empty account field.
I am not able to say whether this issue is more Jira/CFL fault with
their quite stupid implementation of creating issues in Jira from
Confluence, or Tempo fault with that -1 for "None". I'd just love to
see it working in Behaviours.
I am also not able to tell whether more people are affected/limited by
current behaviours.
Have a nice day!
Generated at Sat Jan 22 12:33:42 UTC 2022 using Jira
8.13.13#813013-sha1:3ab5fbe7b6c572b1ee4ccec98a9f447334884e00.