Workflow Steps for Jira 

Available for Jira Server, Data Center and Cloud

What: Not every query is necessarily a ticket, questions may be directed to a team first before deciding if an issue is needed. If it is needed, then a new issue can easily be created, pulling in the relevant information into Jira for the issue to be worked on. 

How: Assigned emoji added to message.

Why: No repetition of information and time saved copy and pasting, as well as context-switching.

What: You've just demo'ed a new product feature, shared a piece of content or hosted an event; how do you get feedback from your colleagues? Send out a message in Slack. When people respond, add an emoji to the comments you want to save and add this to an existing issue you’ve created to collate comments.

How: Dedicated emoji added to message.

Why: Making information useful and easily findable in dedicated space rather than trawling through Slack threads.

What: There will always be a dedicated set of tasks for new starters in a company, whether it’s compliance assessments, updating bank details or requesting equipment and software. When someone joins and they’re added to a dedicated channel (by #department, #team or #new-starters), automatically assign and point them in the direction of tasks they need to complete. 

How: Workflow starts when someone joins a #channel.

Why: No repetition or time wasted from the onboarding team or departments involved to ensure new starters are onboarded correctly.

What: Whether it's weekly status reports, bi-weekly team presentations or monthly expenses, regular tasks are sometimes the easiest to forget. Set these up as regular reminders in Slack to prompt you for the information needed and either dismiss it or fulfil the item right away. 

How: Set up once to receive scheduled reminders in Slack. 

Why: Automate common tasks and combine your tech stack for maximum efficiency.