Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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
4,455,617
Community Members
 
Community Events
175
Community Groups

Tell us how you've implemented Change Management

Edited
Amaresh Ray Atlassian Team Sep 08, 2019

Hello Community 👋,

I'm a product manager at Atlassian, looking at improving change management capabilities across our products. In particular, we're looking at bridging the gap between Dev & IT/Ops teams. 

If you're interested in speaking with us, please sign up at https://forms.gle/c5Xv3vPLiKc68tNk9 and we will reach out to you to set up a 60 min phone/video call over Zoom.

In return, we'll be happy to offer you a $100 gift card to thank you for your time.

Thanks!

Amaresh

5 comments

I miss a lot of features from another tool, in some steps of "classic" change management. 

- collect tech impact, create tasks for teams, organize a cab meeting.... 

- a way of have the calendar to plan the changes (without apps of course). 

- worflow automation to enable triggering other processes, and so on. 

from my point of view, the change requests issue type is the less effective in the ITSM default flows in JSD. 

Integration with tools that perform deploy 

I.e why not integrate bitbucket to this process? or with jira service desk as a whole?

i would like to contribute with you in this.

Like # people like this

I second this observation for all the reasons sited. I gather that this is where Jira Software and Jira Service Desk integration may assist. 

However what we have found in our 2 years of using JSD alongside UM e.g. Skype for Business that our user prefer to request changes via chat/Screenshare and report incidents via email (change management to convert to portal only is on the way). 

In our specific use case it would be great to get integration between  Jira Service Desk and Microsoft Teams.  

Like Deepanshu Natani likes this
Amaresh Ray Atlassian Team Nov 24, 2019

@Patricia Francezi and @Dwayne Pierre thank you for your feedback. I would love to chat you further to learn more about your use cases -- please send me an email at amaresh.ray [at] atlassian.com and we can arrange a time to chat!

Like Deepanshu Natani likes this

I agree with Patricia.

 

We need tasks that can be issued to different departments. After task 1 is done, task 2 is sent to the next department e.t.c. After all the tasks have been marked done, the Change has been implemented and can be reviewed.

 

Also, the Change calendar should be a free widget inside Jira, both inside the project and for a dashboard.

 

When you are working on a Change request, it would be great to be able to see some portion of that calendar also, on the same page and in real time.

Like Dwayne Pierre likes this

Second this observation. 

 

@Viktorhave tried to accomplish this via workflows? 

I agree with this as well, except that the tasks for different departments need to run concurrently sometimes.  For instance, an employee changes department and requires different licensing/software, possibly hardware, and business card changes, etc.  You don't want any tasks getting held up, so it should be a shotgun effect.

I support this extension - our client's change processes are often complex, we need the ability to structure activities in a flow that could have parts that are sequential, other parts in parallel. Then we need 'dependent' activities, which means a step in a Change process needs to wait until another Change has completed. We have to do this now with scripting so a better native capability would be great.

IT wise, created a massive workflow w/ associated fields that went through an Engineering Review Board, and Configuration Control Board. All steps were of course developed in house per requirements. 

Had multiple levels of approval for each step, especially with IA , Team Leads, and Management since we deal with IT systems. It was pretty vast and got great feedback from division management. 

Like Patricia Francezi likes this

Make Components more customizeable to be able to use in Approvals.

 

Adding a group as a component lead that can approve requests regarding that component is one use case.

Like # people like this

What I really miss in JSD is to be able to set an agent "out of office". We use some grade of auto assign issues, but if that assignee is out sick or on holiday, I would like to be able to set a second or third named agent to cover for the agent that is "out" I have seen other ITSM systems where "agents" can reserve them selves for assignements, and issues then gets auto-assigned to the next on the list..

@Jørgen Sandtorv , I can recommend to you an exellant app for this feature - Out Of Office Assistant.

Like Jørgen Sandtorv likes this

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events