We have been doing a couple of field name changes e.g., component becomes team and priority becomes severity, for quite a while. I discovered today that the Advanced Search function is still looking for the old field names. If I try to use the new field names I get an error saying the field does not exist. Is there anything I can do to get around this? I hate to have to send out a list of alternate field names to users who want to take advantage of the Advanced Search option but those are really common fields in searches.
Has anyone found a workaround for this?
--
Post by ktempesta - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38448_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user