Any update on this? It's been 3 years now since it was 'Being picked up', and there is still no repeatable absence option.
Even if you don't create them to infinity, just 'schedule' 365 days worth of this absence , and link them all back to the original one so that if it is deleted/changed, it updates the others.

Updates?

Is there any progress on this feature? We are already in version 2.2.4. and still it is not possible to have regular days of in the week. The possibility prevents project managers to plan people on days they are not in. It is a major influence on releases because if a certain developer isn't working on Fridays and Mondays but you have to wait for him till the next Tuesday you will have release and sprint problems which do not show up in Portfolio because the calculation will still plan with available hours in that week. 

In this case Portfolio will calculate that the release will be on time but in real life you will not be on time.

Splitting this up into a couple of separate requests - see the linked issues. For those looking for global non-working days such as national holidays etc., this is covered in https://jira.atlassian.com/browse/JPO-295 and will be shipped first, as part of 1.9. I'm keeping this issue open specifically for the aspect of defining a repeating cadence of absences, which is not yet covered as part of the changes in 1.9.

Thanks for picking this up!
The ical import would be great for the national holidays in my opinion, otherwise we're stuck with manually entering those.

For the original request, I still think it would be sufficient to have an option "repeat weekly/bi-weekly/monthly" on each non-work interval. This should cover this use case. Having another google calendar just for weekly/monthly dates ist too much overhead.

I'm currently investigating solution approaches and want to pick up this topic for one of the next dev iterations.

Right now, I'm considering the following solution:

• A plan-wide setting for work hours per day (currently a static value of 8 hours/day is applied)
• A plan-wide setting for working days (Mon-Fri is the current default, makes this configurable)
• a plan-wide setting for non-working days such as national holidays etc - these apply for all people in the plan.

Next to that, the option to overwrite this on team level (a team might be in a different Geo location and have different working days)

All of this would not yet cover juri.vonkrause's original requirement. As for this: Would the idea posted by rakuten work with the possibility to supply an ical/ics link for individual team members (multiple members could use the same link/schema)? If we allow this, we'd probably have to make some conventions as to what we read from the calendar. For example, only take full-day absences right now as scheduling doesn't consider exact times of the day.

Any further input appreciated if you see these considerations not yet addressing your particular requirements around working days.
Thanks!
Martin Suntinger, PM for JIRA Portfolio

This causes us an issue too. Makes Portfolio more inaccurate as time goes on.

Would also really appreciate this feature.

Regular days off will be a problem for some teams, but unless I'm missing something, national holidays should be a problem for every JIRA Portfolio user in the world. Having to enter national holidays for every user individually in every plan every year is a major problem in my opinion.

Since all add-ons which deal with scheduling (JIRA Portfolio, JIRA Agile, Tempo, Gantt-Chart add-ons, etc.) need to know when national holidays and other company-wide days off are, it might be nice if there was a place in the JIRA core product where this could be entered, and at least the Atlassian officially developed add-ons could refer to that (with 3rd party add-ons taking advantage of it if they wanted) as the base layer of scheduling info, with team-level days off being layered on top of that.

In fact, you could even provide the option to specify an ics file or URL of a calendar so that holiday information could be retrieved from some source like Google Calendars, saving the admin the trouble of manually entering holiday information each year.

This could be a behaviour similar to the "non-working days" in JIRA Agile.