You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello Community,
So far the solution to make users choosing an issue type is that: adding the dumb issue type like "Choose an issue type" (sure with conditions preventing to create a ticket) and making it the default issue type.
The issue is the type scheme contains Task, and this type as default one cannot be changed to a custom issue type in the scheme - it seems it's the known bug (at least, in v.7.5)
When using behaviours, the initial setting setFormValue("Choose an issue type") for Task works, but except the case when Task is actually needed - it's reset to the above.
So the goal is:
1) when switching to this project, the default issue type is "Choose an issue type"
2) When choosing any issue type, it is chosen
I've played around with this code:
def issueTypeField = getFieldById(ISSUE_TYPE)
//def summ = getFieldById(SUMMARY)
def issueTypeValue = getFieldById(getFieldChanged()).value.toString()
issueTypeField.setFormValue("Choose an issue type")
//summ.setFormValue(issueTypeValue)
if (issueTypeValue == "10000"){ //10000 is Task id
issueTypeField.setFormValue("Task")
}
Summary was used to check values.
Can someone help me out here?
Thanks!