There's not enough information here. Answers is not on version 6.3 and doesn't have configure columns - do you really mean JIRA?
And what do you mean by "script"? And why? If you are talking about JIRA, and you're trying to stop offering fields to users, then you have a nightmare of a job becasue your script is going to have to understand your entire user-to-project-to-field relationships to know which ones it should hide
we have already implemented this in JIRA 5.2 (i.e to restrict a custom field in configure colums of the issue navigator.) we have done this by taking the id of the drop down list of the configure column list via jquery.
where as in JIRA 6.3 the list is being displaying in a different way (by the help of search box).
how can i restrict via jquery..?(which id i have to use)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, one of the many reasons for NOT trying to be clever with javascript - it usually breaks on every upgrade. I'm not sure you can do this as simply as you could in Jira 5.2 - I'd strongly suggest starting again from scratch. Although I really don't see any use for wanting to remove the columns either - my instinct would be not to even bother.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.