We need to drive a bunch of metadata in our JIRA tickets from a searchable autocomplete field which has more than 10,000 entries. We'd like to use this design pattern in multiple ways (searching users, applications, or IT Projects), so a simple user picker is not sufficient unfortunately. When the user selects a value in the autocomplete field, multiple other values on the form will be populated based on the data.
How are people handling this? i doubt i'm the only one looking for a solution here. Looking for something quick and easy to deploy and this is fairly urgent. I'm currently looking at nFeed, we're hopeful this will solve our issue as it seems to allow caching in one place which will reduce the footprint of this substantially. It seems to perform well on our initial tests.
I'm very interested in nFeed, but we've been working with your support already and we're having trouble driving form behavior based on changes to nfeed fields.
For example, if you have an autocomplete for a user where you can search their account number, and when the field gets selected, we'd like to change the reporter field (Prior to saving).
Typical actions would be:
We've yet to find any design pattern which allows us to do something like this using nFeed, as it appears it does not play well with the other tools we use to drive form behavior (behaviors, or jjupin). We tried to use JQuery to do this and found that we couldnt hook into any client side events (like onchange) because upon selection of an nfeed field, the contents of the other fields are blown away and the html is re-written.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot