When working from my backlog the inline issue create feature is not showing up. Why?

[Tyler Anderson]

Over the weekend this issue has popped up. I have checked online and all I could find was if the filter was looking at multiple projects it could cause a problem. I checked and it is only looking at one project and ordering it by rank. 

There were no updates or changes over the weekend, but it worked fine on Friday then was gone on Monday. 

[Andy Heinzer]

I don't know of any changes that would cause this.   There is no configuration setting for this specific option that I am aware of.  

1. Do you still have the ability to create issues in the project(s) referenced by this boards filter?  (ie, using another method aside from this quick create)
2. Are you using Jira Cloud or Jira Server?   If Jira Server, what version of Jira Software is this?
3. Is this a Kanban or a Scrum backlog?
4. Are any other users effected by this?  Or is it only you?
5. Have you tried to utilize another browser to see if this might be a browser specific problem?

Please let me know, perhaps these answers can help us troubleshoot this further.

Andy

[Tyler Anderson]

Hello Andrew,

1. Yes, we still have the ability to create tickets with other methods. 

2. We are using Jira Server v7.8.0

3. As far as we can tell all users have been affected. I have not SU'ed in or sent and email to all users. We checked by SU'ing as well as full teams has reported the problem. 

4. The issue happens across all backlog boards (Kanban and Scrum alike).

5. Tried other browsers and incognito browser. Also, cleared cookies and cache. Nothing has produced a change in outcome. 

Hope this helps. 

Tyler

[Andy Heinzer]

I have not been able to replicate this problem.   Nor have I found any bug reports of this issue creation feature at the bottom of backlogs.   The fact that this is happening for all boards would tend to indicate something system wide is causing this.   I would be interested to see if you can have a Jira administrator look in the announcement banner.  My thought here is that perhaps a customize script placed here would appear on every page in Jira sometimes, depending on the content here, it could cause a weird behavior like this.

If that doesn't help, you could also have your SQL admin run the following SQL queries to see if perhaps any custom field descriptions have included script tags in them:

select * from fieldconfigscheme where description like '%<script%' OR description like '%<SCRIPT%';
select * from customfield where description like '%<script%' OR description like '%<SCRIPT%';    
select * from customfield where description like '039avascript%' OR description like '%html%' OR description like '%css%';
select * from fieldconfiguration where description like '039avascript%' OR description like '%html%' OR description like '%css%';

If both of these turn up no scripts, then I think the next steps I would take would be to see if you can disable the other user add-ons in Jira to see if perhaps this problem is being caused by a plugin to Jira.