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

How to best create a workflow for new web development requests using JIRA and Confluence

I would it improve the process we have at the moment for receiving and managing new web development request. 


Key Requirements:

1. Manage changes in priority

2. Have calculated priority score based on 5 criteria multiple

3. Work can be allocated to separate SCRUM teams with own Project Board and Backlog but all Work Requests reported in a central space

4. All work request need ability to be submitted as a form that integrates into JIRE potentially from Sharepoint (any recommendations for Office 365 integration would be good)

1 answer

0 votes
Brant Schroeder Community Leader Aug 03, 2021

@Jamie Brown Welcome to the Atlassian Community.  

We use Jira Service Management to receive all of our development requests.  We use an automation when the issue is created to set the priority based on some required questions on the form.  These requests are reviewed in a morning standup and then catigorized into 4 different buckets (won't do, low, medium and high)  For low, med or high issues we create a corresponding issues in our software project and schedule them into a release cycle and place it on a sprint.  The two issues are linked and an automation keeps the service desk issue updated on progress.  If the issue is already being worked on we just link the issue.  When the issue is released an automation closes the service desk issue.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events