You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello Fellow Atlassianer's,
We are in the process of migrating Jira to the cloud. We have a rather more unique way of handling our Jira requests. We use Jira Service Desk and its portal to handle questions and report problems. On certain request types, those then get closed and a issue gets created in a Jira Core project. These projects all correspond to a Business segment/department in our company, in which all the managers have Core licenses and can view these projects, and prioritize their requests (literally, they set the priority level of the issues).
When new work is needed, a Jira Software issue is created, assigned to a developer, and linked to the Jira Core business issue. The developer then does their work, recording there efforts to the Software issue, and linking any commits to Git to the issue.
We require QA Testing to be done on development changes, along with a business/UAT sign-off. Currently we have statuses in the Software Issue's workflow that after the developer completes their efforts, they push it to the QA Testing status, in which QA then gives approval that it works as expected. Then it goes to someone in the business line who put in the request that it is also working as they expect and give there approval in the issue. We currently do this using the approval plugin from Herzum. The users get an email and from that email can click to approve or decline.
Just curious what method's or workflow designs others are using that requires similar approvals with Jira.