|
|
Recently I came across a simple requirement and saw an exaggerated estimate for that. Well, it isn't all that rare but I was amused how a different line of thought can make all the difference in the world! Requirement : Make a field mandatory in the workflow screen and make sure the mandatory icon is present on screen. 15 Comments It is actually a follow-up post. A follow-up to the question Mizan asked in my last post. Before you proceed, here is warning: Strictly for AJS novices, like me! In this post, we are looking to prepopulate jira fields based on the current user's group. And we are gonna use AJS for the same! Scene 1: Agile advocate in the room is screaming! How can you have 2 fix versions for a single ticket? How? How? How? Several scenes (and days) later, Scene N: Q: We need to restrict the fixVersion(s) field to have only one version. And we need it before the next meeting. Can you? A: Yup, you are not the first one to ask. Let's do it! | AuthorJobin Kuruvilla - Works in Go2Group as an Atlassian Consultant.   CategoriesAll ArchivesApril 2013 |
RSS Feed