Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do we change 'working days' in Sprints? I want to include weekends.

There is a support article for this but it does not seem like the flow it suggests is available anymore. I'm looking to include weekends in the "days remaining" count

2 answers

Hi @Jake Simon 

Are you using a company-managed (classic) or team-managed project (next-gen)?

The documentation link you provided is for company-managed.  Team-managed projects do not have the ability to set working days yet.  Here is the feature suggestion to add that, which you can vote for or watch for progress:

Best regards,


Looks like we posted the same response at almost the same time :)

Like Bill Sheboy likes this

Woot!  My answer matched one from Trudy!  ;^)

Like # people like this

Hello @Jake Simon 

Are you working with a Team Managed project or a Company Managed project? It will say at the bottom of the navigation bar on the left.

The article referenced is valid if you are working with a Company Managed project.

It would seem that configuring working days is not a feature available for Team Managed projects as per

Thank you! This feature used to be there, not sure why it was removed in 'Next Gen' projects - seems like a step backwards.

Hi, Jake! 

My understanding from community posts is that team-managed (next-gen) is re-implementing and enhancing functions, not porting the old code as-is.  As they do that, no doubt priorities and customer usage are driving the order they build the features, so try to vote for the stuff you need sooner to help them with that.  Thanks!

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

240 views 7 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you