Hey there, Venugopal.
Seems like the feature that you would like to remove is a standard default feature for JIRA itself. Have you considered the approach from the Atlassian Experts to assist you with this? In addition to that, is there any particular reason on why you would like to remove the description of the Component field?
One of the alternatives that you can consider is to change the renderer of the Component field from the Autocomplete Renderer to the Select List Renderer. See how it goes for you.
In response to the question, "is there any particular reason on why you would like to remove the description of the Component field?", while I cannot respond for Venugopal, here is my opinion.
Some descriptions are quite helpful, such as "Story Points - Measurement of complexity and/or size of a requirement". However, some descriptions are self-explanatory, and not worth the additional clutter that they add to the Create screen, such as "Sprint - JIRA Software sprint field".
As new fields are added & removed over time to accommodate the various lessons that our company has learned, it is dangerously easy to end up with a cluttered, messy Create screen that includes more fields than is necessary. I am always looking for ways to keep that screen as simple as possible. Removing descriptions that are not adding value is one way to do this. Arguably the description for Component - "Start typing to get a list of possible matches or press down to select.", is not adding value. I assume that is why Venugopal is asking for a method to remove it.
I received a request yesterday from a JIRA user that I work with asking if there was any way that I could help him remove the description from a few fields for the reasons described above.
You can modify the description for Components inside the file JiraWebActionSupport.properties located under the <JIRA_INSTALL>/atlassian-jira/WEB-INF/classes/com/atlassian/jira/web/action directory.
Check if the changes are reflecting now. Also you may like to go through this link
# Generic generic.picker.static.desc = Start typing to get a list of possible matches or press down to select.
Alternatively, if still the changes are not reflecting, you need to
NOTE:You need to keep track of such changes during the future upgrades.
We're looking for participants for another workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sh...
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