nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue description onload

srinivasp

In jira 4.0.2, we have a js file that is called on load of issuesummary.jsp file to do some specific operations on the description section of issue. I tried the same in jira 4.4.4 by inlucding the js statements in issuesummary.jsp file but it is not working. Can you please suggest what needs to update in order to call that js from that jsp file?

Thanks in Advance.. Srinivas

Accepted answers

Dieter

Hi Srinivas,

I'm afraid the JS is put a in place where the DOM tree has not been load yet. I suggest you to put the code into a document ready handler like in this snippet

<script>
(function($){
   $(document).ready(function(){
         // do something with description field
   });  
})(AJS.$);
</script>

I'd also recommend to avoid changing system jsp's but put this code into the description of the system field 'description'. Use your own field configuration (scheme) for that. That way JIRA updates are with less effort for you.

Dieter

All comments

Dieter

Hi Srinivas,

I'm afraid the JS is put a in place where the DOM tree has not been load yet. I suggest you to put the code into a document ready handler like in this snippet

<script>
(function($){
   $(document).ready(function(){
         // do something with description field
   });  
})(AJS.$);
</script>

Dieter

srinivasp

Hi Dieter,

Thanks for your reply but i treid other way. I included the js script tag in header.jsp file and then it worked. As the other pages also got effected, i removed the script tag from the header.jsp and added it to issuesummaryblock.vm file since i want the js function to be called only on the onload of issue summary view. It is working now as required

Do you suggest any other way for handling this requirement?

-Srinivas

Dieter

Hi Srinivas, The solution i described would be called only when the description is edited or created. In this case the description of a field is displayed and thus the JS is executed. But i see now that this does not help when you just view the issue. In this case the description of a field is not displayed and thus the JS script is not executed. This could be solved by putting the above code in the system banner and doing a quick check if a field with id description exists. This should not harm performance and usually one eill put more and more jacascript beautifiieing code in the system banner, also because it can be tested easily. Regards, dieter

Dieter

Sorry for the bad formatting, this is what aac creates of text inputted on an ipad

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

summary