Emma Ysebaert Atlassian Team

@Hayden Davey unfortunately not at present, however I've opened up a new feature request to add flexible naming for financial years which you can watch/up-vote. Please also comment if you feel there's any additional context which may be useful? https://jira.atlassian.com/browse/JSWCLOUD-26838

@Rafael_Silva @Hayden Davey We have followed convention for FY naming. Fiscal years are named using the year when the period ends. For instance, a fiscal year that runs from 1 April 2023 to 31 March 2024 is called FY24

Hi @David Pezet , Myself and one of our support engineers have tried to replicate the issue your experiencing on our own test instances without any luck (same time zones you specified applied). We'd really like to understand why this might be happening on your site and resolve the issue for you. Are you able to get in…

Hi @Tanvir Hossain , As mentioned above, this feature is currently only available in our Cloud version of Advanced Roadmaps. There is some interest in having this added to the Data Center version - I'd suggest adding your vote to this existing feature request to show your interest:…

Hi @Rob Horan , Thanks for spotting this - keen eyes! I'll let our Content Designer know and have it updated asap - watch this space :-) Thanks again, Emma

Hi @Akira Mitchell , It looks like we may need to update our docs... the view settings you need for this view are group by team (not sprint), with the show capacity box checked. Hope this helps, and i'll make sure we get our docs updated! Emma

Hi Krzesimir, The interface you're referring to is our 'Live Plans' application, which we ended support for on 31st July this year. Unfortunately, there is not currently a way to achieve the behaviour you're looking for in the redesigned interface - but we love to hear feedback like this, and will definitely keep this in…

Hi David, You can see a sum of the story points for all items in an epic by checking the others box for Roll-up in the view settings panel. This will then display the sum in the story points field: Regards, Emma

Hi Dani, You can achieve this within Advanced Roadmaps in a few different ways: 1. You could configure your plan to exclude the Initiative issue type (configure -> exclusion rules): 2. You could visually remove these from your timeline using the hierarchy filter (go to filters -> select the level below initiative as the…

Hi Steven, This is definitely possible. Just head to your View Settings panel, and check 'others' in the roll-up section: This will populate the roll-up of days in your estimate field. Hope this helps! Cheers, Emma

Hi Lionel, Could you confirm for me what version of Confluence and what version of Portfolio for Jira you are using? The macro only requires a valid confluence sharing url. As a sanity check, can you paste that copied confluence sharing url in a new browser tab and check that it renders correctly? Emma

It's interesting that portfolio is not liking something about this particular JIRA board. Without being able to see log files or console errors, I'd be stabbing in the dark to work out what might be wrong here. It might be helpful to compare this board configuration to other boards that are working correctly in portfolio.…

Happy to help! Regarding auto-scheduling, if it's scheduling 0 tasks, that just means the algorithm has no optimisations to make (your plan is perfect, congratulations!). If you wanted to see some auto-schedule changes, you would need to make changes to your plan, for example your auto-schedule settings, team sprint…

Hi @Ron Grosberg , Thanks for getting back to me with that info. I've tried to replicate your scenario with a nested warning in autoschedule with group by/filter by team applied. I've tested on Firefox 68 on Mac and Windows, and I can't seem to reproduce the mouse cursor flickering behaviour. I'm wondering if this may be a…

From the screenshot I can see that the page scripts have loaded, as the loading indicators are displaying. These continue to display while the scripts attempt to retrieve the backlog data for the plan, so there's either going to be an error retrieving the backlog, or an error processing the data that's returned. I can't…

Are you seeing any errors in the console or the network tab?

Hi @Calvin Senteza , I'm sorry you're experiencing this issue. Could you let me know what version of Portfolio for Jira you currently have installed, and also which browser/version/platform you're using? Thanks, Emma Portfolio for Jira team

Hi @Ron Grosberg , Thanks for getting in touch, and I'm sorry you're experiencing this issue. In order to better understand why this might be occurring, I was hoping you could help me with some further info: * What is the Firefox version you are using? Are you on Windows or Mac? * Do you have any particular view settings…

@Robin Klein glad we got to the root of the cause! I'm very interested in working out why this was displaying a task issue type instead of sub-task. I will investigate further and try to find a way to have a meaningful error displayed. Regards, Emma

Hi Robin, Thanks for getting in touch, I hope I'll be able to help with your query. I haven't been able to replicate this issue type mismatch on my own instance, but I have a hunch that this may somehow be related your required field configuration. Looking at your screenshot, I don't think you shouldn't be seeing this 'Set…

The new planning experience I was referring to above is part of the Server offering, however Cloud is also developing a new planning experience called Jira Software Premium. If you follow this link, you'll get to explore the new offering, and you can join the waitlist for the Early Access Program to start trying out the…

Hi Mikal, If the Status filter doesn't solve the problem, it may be that you need to change the Completion date filter that is applied to the plan. The default completion date is 30 days, and you can set this to a custom range by selecting More -> Completion Date. This will create a new Completion Date dropdown to the…

Hi Mikal, Apologies, the instructions above were for the new planning experience. To achieve this in your current planning experience, you can set a status filter: From the More dropdown, select Statuses: This will create a new Statuses dropdown to the right. Select this, and you'll be able to select only the statuses you…

Hi Mikal, In your configuration page, in Issue Sources, the default value for Completed Issues is 30 days. Any story that has been closed within this period (Epic's included) will stay in your plan until that period has passed. If you reduce this value to 0, your completed Epics and stories should no longer appear in the…