JIRA Agile Server Knowledge Base Archive
Related content
- No related content found
Last modified on Oct 8, 2015
In this section
- Cannot Add 'Remaining' Field in the Lower Right Corner of the Card
- Customized Issue Types with No Card Colors throws Errors
- Unknown Card Color Strategy
- When I edit or transition an issue, the issue history records an edit to the Sprint field
- Clicking on the Agile tab always redirects the user to the "Getting Started with JIRA Agile" page
- Detected an error (BundleException) enabling the plugin 'com.pyxis.greenhopper.jira'
- Stacktrace Invocation of method 'isPriorityViewable' when Viewing Planning Board
- Troubleshooting Contexts
- Troubleshooting Boards - Chart
- Cannot Create or Edit Context throws ClassCastException
- Context Filters Stuck on Old Usernames
- Filter Not Listed In JIRA Filter Box When Adding/Modifying Context In Classic Boards
- How to Remove Corrupted Context?
- Accessing the Chart Board leads to NullPointerException: at com.pyxis.greenhopper.charts.CurveChart.getRatioCurve
- Jira Software boards not visible after filter deletion
- Charts Contain Unreadable Font and out of Axis Range
- JIRA Agile Chart Board not Displaying due to 'No fonts found' Error
- JIRA Agile Control Chart Display Erroneous Values
- Cards Appear in the Planning Board but not in Task Board
- Compact (Kanban) Option does not Appear in Task Board Views
- Continuous hour glass spinning on edit of classic Scrum project templates
- Invocation of method 'isFaded' stacktrace when Accessing Task Board
- java.lang.String cannot be cast to java.util.List in TaskBoard Transition
- JavaScript Loading Icon Endlessly Spinning on Task Board
- NullPointerException is Thrown on Task Board when Missing Full Name on User
- JIRA Agile Crashes with "divide by zero" Error Message only when accessing the task board
- Remaining Estimate field shows NA instead of Zero when Resolving Issue in Task Board
- Sub-tasks are not Correctly Associated with Parent Issues in Jira
- Unable to Display Task Board due to Corrupted Version Data
- Unable to Perform Issue Transition on Task Board
- Unable to Set Comment Field as Required on Transition Screen
- Cannot read property 'DEF_DATE_FORMAT' of undefined when Viewing Rapid Board
- 'AJS.params.JiraVersion is undefined' when Viewing Rapid Board
- "This version of JIRA Agile requires sprints on Scrum boards to be migrated" announcement banner persists after all boards had been migrated
- $ is not a function error thrown by browser
- Agile boards all presents a blank screen
- Agile Boards Unavailable in JIRA Agile After User or Filter Deletion
- Agile swimlane based on query stopped working
- Changing a Rapid Board Rank field
- Clicking on Issue Link in Rapid Board results in Internal Server Error
- Error: The issue no longer exists in JIRA Agile
- Exception moving card on Rapid Board
- JIRA Agile appears to calculate Story Points inaccurately if changed during a Sprint.
- JIRA Agile Board Error Invalid numeric type
- JIRA Agile boards not displaying scroll bar
- JIRA Agile Exception Occurs due to Third-Party Plugin
- Edit of an issue throws Uncaught TypeError error in Jira server
- JIRA Agile Rapid Board exception "NREUMQ is undefined"
- JIRA Agile throws Internal Server Error when trying to Manage Boards
- Manage Rapid Boards throws Cannot bind new shortcut Exception
- Not able to "Drag and Drop" in Rapid Board
- Plan Mode does not display
- Rapid Board is Empty
- Rapid Board Error showing Exception: Script Error
- Cannot create Rapid Board with 'ERROR: relation "public.AO_60DB71_RAPIDVIEW_ID_seq" does not exist'
- Erroneous error ${action.projectConfig.getCardColor($type)} is not a valid reference
- Configurable Card Colours for Issue Parameter Visibility
- Error accessing JIRA Agile: OrderableField cannot be null
- Error while creating Scrum Board sample data
- Exception: NS_ERROR_FILE_CORRUPTED
- How to get accents to work on Rapid Board quick filters
- Getting error while migrating the scrum board in Plan mode
- Issue ranking not working on a Kanban board
- Internal Server Error on Rapid Board
- Rapid Board needs at least one column which maps to at least one status
- Removing Issue from Running Sprint in the Rapid Board results in Bad Request
- Safari board rendering problem
- Santander's browser extension for Chrome browser throws exception in JIRA Agile
- Scrum boards are currently unavailable. An administrator must perform a re-index before you can use Scrum board functionality.
- Simplified Workflow button fails with "Workflow Migration did not complete successfully"
- Some shortcut keys do not work in the "Issue detail view"
- Sprint Disappears
- Sprints are Greyed out in Planning Mode
- The board column headers are misaligned
- Unable Access Rapid Board if Story Point is Edited/Set in German(Germany) Language.
- Unable to access Planning mode due to at com.atlassian.greenhopper.service.rapid.RapidViewClauseServiceImpl.getPlanModeClause
- Unable to access Scrum Board due to corrupted index
- Unable to create board in JIRA Agile
- Unable to start sprint and pick date through calendar
- Unassigned issues doesn't follow the swimlane configuration
- UndeclaredThrowableException while Clicking Issues Navigation Menu in JIRA
- urchin Tracker is not defined in JIRA Agile
- When editing issue in JIRA Agile: "Uncaught TypeError: Object false has no method 'getId'"
- Troubleshooting Boards - Rapid
- JIRA Agile "Invalid License Key Specified"
- License Page throws Stacktrace with 404 Error
- JIRA Agile disabled with the error License is for an older version and maintenance has expired
- Error when access into Planning Board and Task Board
- JIRA Agile table does not exist
- Locate Version Hierarchy in JIRA Database
- NullPointerException when Switching between Projects or Boards
- JIRA Import Fails with ORA-02298 Parent Keys Not Found
- JIRA Agile Boards throw ConversionException
- ORA-01461 error when using JIRA Agile with Oracle
- Configuring MySQL 5.7 Database with JIRA 7.2.x or below throws 'Error connecting to database Unknown system variable 'storage_engine' error
- NullPointerException in JIRA Agile due to Corrupt JIRA Components
- Failed to Create New Entry for an Issue Because Conflicting Data Already Exists
- How To Fix "Issue Ranking Operation log entry found where none expected"
- Upgrade to GreenHopper 5.8.x gives Oracle Error ORA-01400: cannot insert NULL into ("AGILEINF_JIRA"."AO_60DB71_SWIMLANE"."DESCRIPTION")
- Upgrade to GreenHopper 5.8.x using Rapid Board gives Oracle Error ORA-01400: cannot insert NULL into ("JIRA44"."AO_60DB71_RAPIDVIEW"."ID")
- JIRA Agile Upgrade fails due to SQLException: 'pk_AO_60DB71_RANK_ISSUE_LINK_ISSUE_ID' is not a constraint
- Error Message - GreenHopper is currently unavailable. This might be because an upgrade is in progress.
- Calendar._SDN is Undefined in JIRA Agile in Swedish
- Head entry is missing in rank table
- Inconsistent structure in Rank table
- Multiple heads found in rank chain
- Lucene Index vs. Rank Index
- Multiple tails found in rank chain
- Outstanding rank operation transaction discovered. Trying to recover...
- Troubleshooting Active Objects
- Rank field migration explained
- The tail end of the JIRA Agile (GreenHopper) Global Rank is missing only
- After upgrading JIRA and Agile Burndown graphs show no information
- Axis of Burndown Chart displaying irregular dates
- Burndown Charts and Timestamps are Incorrect after Restoring XML Backup
- Daily or By Children Option Unavailable in Burndown Chart View
- Deleting an Original Estimate Doesn't Change the Burndown Chart
- Unable to Set 'Start Date' in Burndown Charts in JIRA with French
- Work logged missing and hour burn down chart shows incorrectly after issue reopened and moved to later version.
- Negative remaining value on Burndown chart
- Classic Boards not Available for Projects
- Custom Field with Number Field type Not Appears in the Version Statistics Box
- Error after Removing Subtask in JIRA Iframe
- Unable to log time in JIRA Agile
- Getting 'Invocation of method 'getCursor' in class' error when accessing Planning Board
- JIRA Agile Classic Styling Broken After Upgraded to JIRA 4.2
- Issues or Subtasks are out of Order in Planning Board
- Planning Board Does Not Show All Issues
- Planning Board is Slow when using Classic Boards in JIRA Agile
- Planning Board Never Loads or Times Out
- Ranking on Classic JIRA Agile Planning Board Out of Order after server restart due to incompatible plugin
- Scrum Boards Fail to Open With Re-Indexing Error
- Remaining Estimate doesn't change in the Sprint due to "Generic Event".
- MethodInvocationException Error when Clicking on Agile Tab due to Unreleased Sub-versions
- Ability to Sort Resolved or Closed Issues
- 'Create Cards' Screen Takes Forever to Load
- 'Add Version' Link Missing from Planning Board
- Team Effort does not match Total Time Spent in Burndown Chart
- Unable to Access Planning Mode due to com.atlassian.greenhopper.web.rapid.plan.PlanningModeServiceImpl.getProgressIndicators
- Time Spent Field in Burndown Chart Is Incorrect
- Unable to Enter Project Start Date and End Date in GreenHopper due to Invalid Date Format
- Unable to View Statistics Marker in Planning Board
- Unable to View Boards due to MethodInvocationException
- Troubleshooting Classic Boards - Planning
- "Epic with name 'xxxx' is not unique" error when trying to add an issue to an epic
- Epics render incorrectly in Issue View
- Unable to Search using Epic Link and Sprint on Advance Searching
- All Epic Link data appears to be lost
- Advanced search for has epic link type fails in Jira server
- Epics marked as Epic Status = Done continue to appear on the Jira Software Board
- Agile uses an issue type other than "Epic" as the "Epic" issue type
- Epic Tag or Label is missing on Sprint board
- Issues missing from the Active Sprint when Swimlanes are configured to use Epics
- Fields missing from JQL auto complete due to missing customfieldsearcherkey
- Reindexing fails with expected exactly 2 rows error in Jira server
- Can't see the JIRA Agile Ranking Field after upgrading to JIRA 4.0
- Changes in Ranking introduced in JIRA Agile 5.8
- Changing Issue Rank in JIRA Agile 5.8
- Classic - cannot configure Rank field for project
- com.pyxis.greenhopper.jira.fields.Assignee cannot be cast to com.pyxis.greenhopper.jira.fields.RankingField
- Could not Prioritize Backlog due to Global Rank being set for Specific Project(s) Only
- Current Query does not currently allow ranking Add Rank
- Exception of Invocation of Method 'realPosition' in Class when Editing Ranking Field
- How to find issues from non-started sprints
- How to Preserve the Previous Ranking After the Upgrade to 4.3.x?
- JIRA Agile Operations fail due to Sanity check for setting nextId of issue
- JIRA Agile Ranking Field Type Cannot Load Due to Project View Add-on
- Reboot causes all ranking in JIRA Agile to be lost
- Receiving 'Issue is not rankable' Unexpectedly
- Sorting by Rank does not show expected values
- Sub-tasks Not Ranked Correctly
- LexoRank balancing or manual ranking of issues fails in Jira server
- Unable to rank issues due to permission issue
- Enabling the JIRA Agile plugin gives the error "The call to the JIRA server did not complete within the timeout period. We are unsure of the result of this operation."
- Indexing error: It doesn't make sense to have a field that is neither indexed nor stored
- JIRA Agile has trouble with Turkish locale
- JIRA Agile Installation Fails - Unable to load interface class
- JIRA Agile still Disabled after the Installation
- ORA-01031 Insufficient Privileges Error when using JIRA Agile
- Removing Feedback Related Errors
- Agile Dropdown Arrow Missing After JIRA Agile Upgrade
- Custom Template Lost after upgrade to JIRA Agile 5.5 and above
- Errors in logs after upgrading from JIRA Agile 5.7
- Burndown Chart and Version Time Tracking Statistics are Changed after Upgrading to JIRA Agile 5.2
- Cannot update JIRA Agile to latest version from 6.2.4.1
- Cards Configuration Disappeared after Upgrade to JIRA Agile 4.3
- Hit into an error message when access to a board after upgraded JIRA Agile from 6.4.x to 6.6.x
- Internal Server Error when trying to access JIRA Agile after Upgrade
- java.lang.NumberFormatException when Upgrading to JIRA Agile 5.0
- JIRA Agile Upgrade Duplicate Custom Fields Error Message
- JIRA Agile Upgrade Fails with a NullPointerException
- JIRA Agile Modules Disabled by Default
- Unable to Enable UPM Add-on for JIRA Agile Installation
- StatisticsFieldAO for foreign key RAPID_VIEW_ID
- User unable to create project and board in Getting Started page
- Using JIRA Agile Generates a java.lang.IncompatibleClassChangeError
- Drag and drop is not working due to plugin reloadibility problem
- Incompatible third-party plugin breaks JIRA Agile 6.3.1 on JIRA 6.1
- JIRA Agile upgrade fail due to parse error
- JIRA Agile Upgrade is not Working due to Duplicate plugin found error
- JIRA Agile upgrade to 6.2.2 fails
- Sprints Disappeared After The Upgrade Troubleshooting Guide
- Upgrading JIRA Agile leads to Internal Server Error
- Upgrading to JIRA Agile 6.3.2 breaks JIRA Agile
- Upon Upgrade to JIRA Agile 6.0.1 the Agile Menu Generates an Error
- Installation Failed with 'Unable to enable web fragment' Error
- JIRA Agile 6.2 not compatible with JIRA 5.0
- Sort by Rank is Broken After JIRA Upgrade
- Backlog is slow to load
- JIRA with JIRA Agile Crashes Java with a SIGSEGV Fault on Linux 64bit JVMs
- Non-English Locale Causes Slow Performance Viewing Issue in JIRA IFrame
- Resolving Performance Issues when using JIRA Agile with Firebug
- 'Stats' Link is Disabled in the Planning Board
- Auto Associate New Issue Key to its Epic Field does not Work
- Custom Template Lost after Restart
- Exception is thrown when creating projects based on JIRA Agile templates
- JIRA Agile Project Template Throws Error ' Invocation of method 'getFlagField' '
- Unable to View Project Template due to Invocation of Method 'getPreferences' in Class
- JIRA Agile is Unavailable due to the GhUpgradeTask032 failed
- JIRA Agile Upgrade Hangs During Upgrading shared contexts of project
- Unable to Install JIRA Agile due to Bad Version Number in .class File
- Epic panel is empty and Epic is listed in the Backlog
- HowTo: Hide JIRA Agile Gadgets from Unauthenticated Users on the System Dashboard
- Agile Query Returns -1 Status Error
- Agile Tab Missing due to 'javax.naming.ServiceUnavailableException'
- JIRA Agile Sprint Health Gadget Days Left Calculation
- JIRA Agile Portlet Error
- Cannot Create Issue in JIRA after JIRA Upgrade
- Error when clicking on View in Issue Navigator
- IndexOutOfBoundsException error at JIRA Agile installation or upgrade
- Internal Server Error message is displayed when clicking on the Agile menu
- Issue screen displays error rendering greenhopper-epics-issue-web-panel in Jira server
- JIRA Agile Query Returns -1 Status Error
- Moving Issue from Non-Ranked Project to Ranked JIRA Agile Project causes System Error
- Unable to delete Non-Working Day
- Troubleshooting Installation
- Troubleshooting Portlets & Gadgets
- Cannot read property 'text' of undefined
- Clear Sprint information when cloning JIRA issue
- Error Sprint does not Exist
- How to remove mistyped Estimate
- Internal Server Error is thrown when accessing GreenHopper Scrum Board
- JIRA Agile Boards are greyed out / faded out after an upgrade
- JIRA Agile cannot be enabled after upgrading to JIRA 6
- JIRA Agile unavailable due to upgrade task not completing
- method 'getSidebarHtml' java.lang.NoSuchMethodError when accessing JIRA Agile
- NullPointerException When Trying to Access JIRA Agile Classic Boards
- Rank is not working
- Rank operations in JIRA Agile via REST fails with 500 Internal Server Error
- Starting Sprint results in date exception
- Unable to manage sprint due to the error 'Project Administrator permissions are required'
- How to change the RANK column in the AO_60DB71_LEXORANK table to the correct collation
- How to Identify Which Node is Performing Balance Operation
- How to track epics in the control chart
- Accessing JIRA Agile boards in IE throws "Exception: Unable to get value of the property 'getItem': object is null or undefined" or "Exception: Unable to get property 'renderAllSprints' of undefined or null reference"
- Unable to rank issues after upgrading Jira Software
- Error thrown when accessing or creating JIRA Agile board due to Dead References on Cascading Select custom field
- Installing JIRA Agile gives Error message "JIRA Agile is currently unavailable. This might be because an upgrade task has failed to run or has not not yet completed"
- Issue removed from sprint after editing
- Agile board throws "Exception: TypeError: AJS.HelpTip is undefined"
- Javascript exception thrown in the Backlog mode of JIRA Agile Board
- JIRA Agile is currently unavailable error when Restoring the JIRA Cloud backup to JIRA 6.4.5 with JIRA Agile 6.7.4
- Accessing Jira Agile Board Configuration throws Exception: Uncaught TypeError: Cannot read property 'regionKey' of undefined
- Multiple Active Sprints in Agile Scrum Board when the Parallel Sprint option is disabled
- How to prevent issues created on the agile board from having resolved date set
- Agile throws the error "Uncaught Error: Error calling method on NPObject"
- No active sprint after upgrading Agile
- While clicking on 'Issues' on the navigation bar throws an error 'Exception caught in 500 page null java.lang.reflect.UndeclaredThrowableException' Caused by: java.lang.Exception: Couldn't find board, did you mean one of: Sample Scrum Project?
- Exception: TypeError: m is undefined
- How to disable Jira feedback button
- Internal Server Error when accessing JIRA Agile board in Work mode
- Several actions such as issue ranking, move, export are failing
- Exception: ReferenceError: moment is not defined is thrown when accessing Agile Boards
- Error in Agile Scrum Board
- Scope Change Warning
- The same sprint is displayed across different scrum boards after moving an issue
- agile-board-parameters-resolver Module Is Disabled
- Workflow Action Invalid error thrown when moving an issue between columns on JIRA Agile Board
- JIRA Agile throws object is null or undefined when loading the Getting Started page
- How the JIRA Software Retrospective time pop-up works
- JIRA Agile Fails to Upgrade when running JIRA with Java Version 6
- Sprint Marker Migration Fails after Upgrade due to invalid number error
- Side bar tips keep showing up for one user
- Creating an Issue in JIRA Agile displays a TypeError
- Must have project administration Permission.
- Rank values appear corrupted upgrading to JIRA Agile 6.4 or later
- Agile License Fails Due to Proxy
- "IllegalArgumentException: Passed List had more than one value." when attempting to edit an Agile Board's filter
- ArrayIndexOutOfBoundsException error when creating a new board using Oracle
- Boards are greyed out / faded out after an upgrade
- Exception: TypeError: d is null
- IE 11 Drag & drop causes browser to crash
- Flagged issues do not get marked as flagged in JIRA Agile boards
- Slow-loading Kanban boards in Jira Software
- Jira Software throws UI error when ranking issues on boards
- User avatars don't display as expected
- Cards in Work Mode Covered by Assignee Name
- Unable to Create Card with non-English Character
- Printing of Issue Cards is Broken
- Upgrade with MySQL fails
- Unable to create board in Greenhopper
- Unexpected error decoding stored license for 'com.pyxis.greenhopper.jira': com.atlassian.extras.decoder.api.LicenseDecoderNotFoundException: Could not find any valid decoders WARN message
- Unable to View Image for JIRA and JIRA Agile Report Charts
- The Quartz Job class 'com.pyxis.greenhopper.jira.customfields.GreenHopperRankingJob' cannot be loaded
- JIRA Issue Contains Multiple History Records for the Same Transition
- No Full Name in JIRA causes Stacktrace in JIRA Agile
- JIRA won't Start If using JIRA Agile and Integrated with Crowd
- JIRA throws NullPointerException when Epic Link is corrupted
- JIRA Agile fails to load due to Permission Denied
- Issues cannot be moved to the Story Issue Type
- Deleting Duplicated Locked Sprint Customfield for JIRA Agile
- Could not find a Custom Field Configuration for field 'customfield_xxx', all projects and issue type 'x' -- therefore cannot find the Option for 'Done' epics.
- Agile Version Report - An internal error occurred when requesting resource
- HowTo: Show Rapid Boards prior to Login
- Agile Gadget throws Exception when using 'All Issues' Filter
- Not able to see story points after upgrade
- Lost Burndown Charts of Released Versions after JIRA Upgrade
- JIRA Agile Upgrade Error Due to Rank index was requested before the plugin was upgraded fully
- Accidental changes to Story Points estimates cause spikes in the Agile Reports
Related content
- No related content found
Powered by Confluence and Scroll Viewport.