Hurdle Docs
Go back to Hurdle.dev
  • Introducing Hurdle
  • Integrated or standalone
  • Getting started
    • Workspace setup
      • General settings
      • Managing users
      • Issues
      • Estimates
      • Backlog
      • Workstreams
      • Sprints
    • Integrating with Jira
      • Enabling the integration
      • Field mapping
      • User mapping
      • Common questions
  • Using Hurdle
    • Managing work
      • Projects
      • Issues and subtasks
      • Triage queue
      • Views and filters
    • Backlog refinement
      • Backlog conditions
      • Workstreams
      • Prioritization
    • Sprint planning and tracking
      • Sprint settings
      • Automated planner
      • Adding and removing issues
      • Starting a sprint
      • Active sprints
      • Ending a sprint
      • Completed sprints
Powered by GitBook
On this page
  • Inviting users
  • Changing user roles
  • Deactivating users
  1. Getting started
  2. Integrating with Jira

User mapping

PreviousField mappingNextCommon questions

Last updated 1 year ago

Once a Hurdle workspace is connected to a Jira project and fields have been mapped, users can be synced.

All users who have an issue assigned to them in the connected Jira project will automatically be created in the Hurdle workspace.

To see which users have been mapped after the integration has been enabled, go to Settings > User Management.

Inviting users

After the integration is enabled, while all users who have an issue assigned to them will show up in Hurdle, they will still need to be invited to create a login and account. To invite a user, click Invite to workspace.

A prompt will appear to enter the user's email and select their user role.

If a user is being added as an Administrator, Team lead or Member, the user must exist in the connected Jira project and the email entered here must match the email associated with their Jira account.

Anyone can be added as a collaborator – these users don't need to exist in the connected Jira project.

User roles can be changed at any time.

Permissions associated with each role:

  • Administrator: Administrators have the majority of permissions across the workspace, including being able to add and deactivate members, configure workspace settings, etc. There is no limit to the number of Administrators that can be in a workspace.

  • Lead: Leads are able to configure backlog conditions, create workstreams, and manage sprint series and settings, but they're not able to add/remove users or configure general workspace settings. There is no limit to the number of Leads that can be in a workspace.

  • Member: Members can create and edit issues, prioritize the backlog and/or workstreams, and have work assigned to them in sprints. They cannot invite others to the workspace or manage workspace and sprint settings. There is no limit to the number of Members that can be in a workspace.

  • Collaborator: Collaborators can create and edit issues, and prioritize the backlog and/or workstreams. They cannot have work assigned to them in sprints, invite others to the workspace, or manage settings. There is no limit to the number of collaborators that can be in a workspace.

Once a user is invited, they'll receive an email with a link and instructions to setup their account and join the workspace. Their status in the User Management table will change to "Invited".

When they've created their account and joined the workspace, their status will change to "Active".

Changing user roles

A user's role can be changed at any time. To change a role, click on the user's name in the User Management table and select a new role in the dropdown.

Deactivating users

To deactivate a user, click on the user's name in the User Management table and click Deactivate. Deactivated users will lose access to your workspace. Deactivated users can be re-activated at any time.