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

Timer on Issue Submission

We have 2 iPads in our office that students use to enter support tickets for their laptops, in order to provide us with their name, password etc. How could I set up a timer on the submission which takes the jira screen back to the issue type selection page, so that the issue just entered is no longer visible on the screen?

1 answer

0 votes
Fazila Ashraf Community Leader Dec 01, 2022

Hi @BrightonSS_IT 

Welcome to the community!

May be usage of "Issue collector" could help you with this use case? ->

Thanks Fazila, not sure if this will be the best solution for us. Even if the submit button was coded to go back to the issues selection (ie. laptop repair, ipad repair) without the use of a timer, that would be fine as well. The problem is that the submitted issue stays on the screen, which means that the student's password is exposed to other people that come close to the ipad.

Fazila Ashraf Community Leader Dec 01, 2022

@BrightonSS_IT  , i was suggesting issue collector to embed in a webpage to only collect the inputs in a custom form and then send to JIRA as a new ticket. 


If you think it is too complex of a solution, can you give a thought about controlling the permissions in the project?

May be the logged in accounts in the ipad can have only the create issue permission and not "Browse" permissions?

That would make them only create the tickets and not view the ones that are created.. (even the ones they created)

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events