Forums
Home Product Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Creating issues from greenhopper view broken

Ahmad Soliman
Ahmad Soliman February 6, 2013

when attempting to create an issue from the green hopper view whether by clicking +Create Issue from the top right corner, or (and more importantly) by click +Create issue in epic on any given epic. The issue is created in the background, is NOT connected to the epic and the following error is displayed.

An error occurredHide…

Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues.

Details

Exception: TypeError: $ is undefined

Resource: http://<servername>:8080/s/en_US8ez3r-418945332/813/3/06f335705a7ff4e901d444f3b89031f4/_/download/contextbatch/js/gh-rapid/batch.js

Line: 1181

Environment

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0

Answer
Watch
Like DIM likes this
862 views

6 answers

1 accepted

1 vote
Answer accepted
Ahmad Soliman
Ahmad Soliman February 13, 2013
Actually, this is different. We turned off feedback to remedy this issue, which in turn causes the issue in having now. Turns out this is a duplicate report of https://jira.atlassian.com/browse/GHS-7317
Reply
1 vote
John Chin
John Chin
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 7, 2013

Hi,

It seem that you found the related problem below, kindly use the KB for temporary solution.

https://confluence.atlassian.com/display/GHKB/Removing+Feedback+Related+Errors

Reply
0 votes
Ahmad Soliman
Ahmad Soliman February 13, 2013
Actually, this is different. We turned off feedback to remedy this issue, which in turn causes the issue in having now. Turns out this is a duplicate report of https://jira.atlassian.com/browse/GHS-7317
Reply
0 votes
Ahmad Soliman
Ahmad Soliman February 13, 2013
Actually, this is different. We turned off feedback to remedy this issue, which in turn causes the issue in having now. Turns out this is a duplicate report of https://jira.atlassian.com/browse/GHS-7317
Reply
0 votes
Ahmad Soliman
Ahmad Soliman February 13, 2013
Actually, this is different. We turned off feedback to remedy this issue, which in turn causes the issue in having now. Turns out this is a duplicate report of https://jira.atlassian.com/browse/GHS-7317
Reply
0 votes
Ahmad Soliman
Ahmad Soliman February 13, 2013
Actually, this is different. We turned off feedback to remedy this issue, which in turn causes the issue in having now. Turns out this is a duplicate report of https://jira.atlassian.com/browse/GHS-7317
Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Copyright © 2025 Atlassian
    Privacy Policy Terms Security
    Welcome illustration

    Welcome to the new Atlassian Community

    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.