Here are the poll results for the Jira Scary Stories series. These are opinion questions – there’s no one correct answer. See all poll questions here or access individual stories and polls from the links in the right sidebar.
Jump to results:
- Security Horror
- Team-managed Project Poltergeist
- Password Fright
- App Update Scare
- Reporting Nightmare
- Backlog Burial
1. Security Horror
How would you solve the problem?
29%
(5 votes)
Reset passwords as needed
0%
(0 votes)
Train users to reset their own passwords
47%
(8 votes)
Ask users to contact the Help Desk instead of the CEO
24%
(4 votes)
Connect to network credentials (E.g., Active Directory, G Suite)
12%
(2 votes)
Recommend secure password management software
0%
(0 votes)
Record passwords so you can remind users when they forget
12%
(2 votes)
Move tools behind a firewall
12%
(2 votes)
Add SSL to encrypt traffic between the browser and web server
24%
(4 votes)
Other
Total Votes: 17
2. Team-managed Project Poltergeist
How would you handle team-managed projects?
0%
(0 votes)
Let all users create team-managed projects
43%
(9 votes)
Let a subset of users create team-managed projects
14%
(3 votes)
Only allow application admins to create team-managed projects
43%
(9 votes)
Only use company-managed projects
5%
(1 vote)
Other
Total Votes: 21
3. Password Fright
How would you solve the problem?
75%
(12 votes)
Reset exposed passwords
75%
(12 votes)
Remind users not to share passwords
44%
(7 votes)
Remove passwords from Jira issues
19%
(3 votes)
Remove passwords from the Jira database
6%
(1 vote)
Other
Total Votes: 16
4. App Update Scare
What would you do?
44%
(7 votes)
Request funding for the app
31%
(5 votes)
Rollback the app version
19%
(3 votes)
Research alternative apps
31%
(5 votes)
Would not have clicked the "Buy Now" button
19%
(3 votes)
Other
Total Votes: 16
5. Reporting Nightmare
What would you do?
65%
(11 votes)
Add the missing selections to the components list
65%
(11 votes)
Explain the pros and cons of components and labels
12%
(2 votes)
Use components and labels together
6%
(1 vote)
Publish the label strategy to central location (E.g., Confluence)
6%
(1 vote)
Other
Total Votes: 17
6. Backlog Burial
How would you improve this situation?
6%
(1 vote)
Use Jira Product Discovery
38%
(6 votes)
Create a separate "ideas" Jira project
19%
(3 votes)
Store ideas in a separate Atlassian application (E.g., Confluence, Trello)
13%
(2 votes)
Store ideas in a separate non-Atlassian application
19%
(3 votes)
Define when ideas are entered into Jira
56%
(9 votes)
Introduce a backlog refinement process
56%
(9 votes)
Create a prioritization and scheduling process
6%
(1 vote)
Other
Total Votes: 16