Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,639,511
Community Members
 
Community Events
196
Community Groups

Restricting Sprint field to get list of sprints matching a pattern

Hello Team there is a pattern roll-jan-2022, rolls-aug-2023, etc like rolls-mmm-* which should be matched before listing the sprint list for the project; non-matching the sprint will not be showing up.

Using behaviour or groovy how this can be done

 

1 answer

1 accepted

1 vote
Answer accepted
Peter-Dave Sheehan
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 10, 2022

This is a late response... let me see if I can help you out a little bit.

I think your question is a little vague, which might explain why no one tried to answer.

But I think I understand.

You want to limit the list of Sprints available in the script field using behaviuors so that only sprints with a name that matches your pattern are visible. All others should be hidden.

I don't think that's possible.

With behaviours, you can use the "setFieldOptions()" method to adjust what's available in a regular customer field that lists "options". And you can use that same method to adjust "Issue type" 

But sprint is a special type of field that queries an api just when you open the dropdown orwhen you search/typeahead (the options are not loaded with the form initially). Behaviours are not able to intercept this logic.

Thank you for the direction

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events