Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Forms Use Case: Recruitment

This is a Forms for Jira Service Management Use Case. We’re publishing a series of these use cases here on Community to share how teams are using Forms to deliver high velocity service. Click here to see all of the published Forms use cases currently published.


HR needs to work in collaboration with teams that are hiring to manage candidates from application through to offer.

Who’s involved?

  • HR Rep

  • Candidate

  • Interviewers

  • Hiring team

Typical Issue Life Cycle

  1. HR sets up a JSM project to manage the recruitment and gives designated members of the hiring team permissions to the project.

  2. Candidates submit their Application forms via the Jira Service Management portal.

  3. When the Application forms are submitted, a request is created and transitioned to the HR SCREENING status. A Candidate Screening form is automatically added to the issue.

  4. HR screens the applications to ensure they meet the minimum requirements HR SCREENING. If an application does not meet the minimum requirements, HR can transitions the request to REJECTED and a notification email will be automatically sent to the candidate.

  5. Applications that pass the HR screening are then sent to the hiring team. The team creates a shortlist of candidates they wish to interview, transitioning those issues to INTERVIEWING. An Interview and an Interview Decision form are automatically added to the issue.

  6. Interviews are conducted and each member of the interview panel records the results on an Interview form.

  7. After interviews are completed the interview panel discusses their opinions and complete an Interview Decision form for each candidate.

  8. The team selects the preferred candidate and transitions the issue to DUE DILIGENCE. A Reference Check form is automatically added to the issue.

  9. Runner up candidates can be transitioned to the PARKED status until it is confirmed that the preferred candidate is accepting the position.

  10. Upon successful reference checks, an Offer Letter form is added for the preferred candidate. When the form is completed, a PDF which can be sent to the candidate or printed for their HR file, is automatically generated. The issue is transitioned to PENDING ACCEPTANCE.

  11. A Decline Letter is added for the candidates that were not chosen. When the form is completed, a PDF which can be sent to the candidate is automatically generated.

  12. The preferred candidate accepts the offer and the issue is transitioned to HIRED.

  13. The process is complete and HR can archive the project.

Set up

Form Settings

  1. Set the Application form to Lock on submission.

  2. Set the Decline Letter form to generate a PDF on submission.

  3. Set the Offer Letter form to generate a PDF on submission

Automation settings

  1. Set up an automation to automatically add the Candidate Screen form when an issue transitions to HR SCREENING.

  2. Set up automation to automatically add an Interview form and an Interview Decision form when an issue transitions to INTERVIEWING.

  3. Set up automation to automatically add a Reference Check form when an issue transitions to DUE DILIGENCE.

  4. Set an automation rule, triggered when the issue transitions from HR SCREENING or TEAM SCREENING to REJECTED, that sends a notification to candidates telling them that their application is being declined.


hr use case - workflow.png


  • The Application form uses conditional logic so the candidate will either be asked to attach their résumé/CV or to complete the work history/education sections of the form.

  • The Screening form can be set to lock on submit, ensuring changes cannot be made to HR's assessment of eligible candidates.

  • Multiple copies of the same form can be added to an issue. For instance, each member of the interview panel can add their copy of the Interview Results form to the issue. This ensures that issue has complete documentation of the hiring process. Alternatively the panel can collaborate and only fill out one form per candidate.

  • Issues can be PARKED at any time, for cases where you want to wait until hiring has been completed before rejecting a candidate; or for holding an application for future job openings.


Each form listed below is available as a Jira Service Management form template within the form builder. Learn more about creating and editing forms here.


 hr use case - form 1.png

Candidate Screening


hr use case - form 2.png 


 hr use case - form 3.png

Interview Decision

hr use case - form 4.png

Reference Check

hr use case - form 5.png

Decline Letter

decline letter.png 

Offer Letter

offer letter.png


Fabian Lim Community Leader Feb 15, 2022

Hi @Peter Preston

Thanks to your posts we were able to create a Jira Service Desk in less than 10 minutes with the default Jira forms.  I will post a video of it how easy this is.  The amount of time this saves instead of having to create the annoying custom fields is just amazing. Also the UI is very intuitive.  


Like Peter Preston likes this

Woohoo! That's great news, @Fabian Lim

Looking forward to the video 🎥


Log in or Sign up to comment

Atlassian Community Events