FAQ

1. Why am I seeing a 500 Internal Server Error while opening the Backlog page?

A 500 Internal Server Error usually indicates that the server encountered an unexpected problem while processing your request.

Possible Causes:

  • The server is temporarily unavailable.
  • The backend service loading backlog and sprint data is not responding.
  • The database connection failed.
  • The application is currently under maintenance.

What You Can Do:

  • Refresh the page after a few minutes.
  • Sign out and sign back in.
  • Check your internet connection.
  • Contact your system administrator or support team if the problem continues.

2. Why can't I create a new sprint?

If clicking Create in the New Sprint modal does not work, the inputs may be incomplete.

Possible Causes:

  • The Sprint Name was left blank.
  • The Start Date or End Date was not selected.
  • The Start Date is configured later than the End Date.
  • Your account lacks sprint management permissions.

What You Can Do:

  • Ensure the Sprint Name field is filled out.
  • Select valid Start and End dates.
  • Verify that the Start Date occurs before or on the End Date.
  • Contact your system administrator if access permissions are required.

3. Why are no tasks showing up inside my sprint?

If your sprint shows "No tasks in this sprint", no work items have been moved to it yet.

Possible Causes:

  • Issues created in the backlog have not been dragged and dropped into the sprint container.
  • Active search or filter options (Task Type, Priority, Status, Tags) are hiding assigned items.

What You Can Do:

  • Drag and drop issues from the Backlogs panel on the left directly into the Sprint container on the right.
  • Reset all top filter dropdowns to All and clear text from the search bar.

4. Why am I unable to add or create a new tag?

Tags must meet system validation rules before being added.

Possible Causes:

  • The tag name field is empty.
  • A tag with the exact same name already exists.
  • Network delay prevented the server from saving the custom tag.

What You Can Do:

  • Enter a unique tag name in the tag creation input field.
  • Ensure you click the confirmation checkmark or Okay button after defining the tag.
  • Refresh the page if the new tag does not appear immediately.

5. Why am I seeing a 403 Access Denied or Unauthorized message?

This message indicates that your user role does not have administrative privileges to modify backlogs or sprints.

Possible Causes:

  • Your assigned role is set to view-only.
  • Your login session has expired.
  • You are not explicitly assigned to the selected project (swiggy project).

What You Can Do:

  • Sign out and sign back in.
  • Ensure you are using the correct user account.
  • Request administrative permissions for sprints and backlogs from your system administrator.
← PreviousBacklog
Next →Sprint