Earl McCutcheon Atlassian Team

Hi Emmanuel, Sure thing, and happy to help out. Also, I was playing around with this query a bit more as it was bugging me that CONCAT() only allowed passing 2 options where CONCATENATE() would allow for as many as you wanted to pass in, but the TEXT() variable would not come through when passing into the CONCATENATE()…

Hi Annette, Once you have created a cross project release in the Plan and associated the projects to the release as covered in "Creating and configuring cross-project releases" adding the issues to the release can be done either by setting the release in the "Releases: column: OR you can set the version in the issue…

Hi Nate, Thanks for the clarification and I misread that the first time, and this is odd behavior. We did a bit of testing and digging on this one, but neither I nor my associates have seen this particular behavior before and we want to take a closer look at the data on your site to see what is going on as looks like a new…

Hello, The Cloud container itself has automated backups taken regularly for disaster recovery scenarios, like a node crashing at the data center, and all the disaster recovery options would be done in the background, and a more detailed breakdown on the services are covered in our "Data storage FAQ" However as this covers…

Hi karen, Getting an unestimated issue to show up on the schedule should work if you set up target dates and view the Target schedule. An unestimated issue will be scheduled when it has either a sprint, a release, or targets dates assigned to it. Additional details on Scheduling unestimated items can be seen in the…

HI Emmanuel, Thanks for the confirmation and follow up with the second solution I'm sure it will help out others if they run into this thread. And just to provide a little clarification on whats occuring is that the main thing you run into is that the input for the JQL needs to be recognized as a string so throwing in a…

Hi Megan, Thanks for the clarification, I got thrown off from the screenshot and I got the New issue view "Issue Layout" settings for mapping fields that you are looking at confused with the Next-Gen Issue type settings for the similar setting in the next-gen projects. For the section you are looking at there is a…

Hi Emmanuel, I can see three conflict points in the formatting, first you are using semicolons ";" as the seperator and this should be a comma ",". Next, the quotation marks around the date need to be escaped and in the "Jira for sheets" application, it uses a second set of quotes to do this, so ""date"" And finally with…

Hi Nick, This happens when a workflow has a status without outgoing or incoming transitions, and then cannot be edited while active. Some more details can be seen in the following KB article: * "Cannot Add Transitions or Delete Steps in Draft Workflows" But the best way to make the edits is to copy the existing workflow so…

Hi Balu, Thanks for the clarification on the platform, and it looks like there is currently a Bug in cloud on Bulk rest api calls that causes the DB connection errors to occur on a rate limit, and the X-ray tests must be triggering the rate limit exception in the bug. More details can be seen here: *…

Hi Nicolas, Migrating cloud to cloud, the portfolio data should come through without issue, you will want to follow the "Migrating from one Cloud instance to another Cloud instance" guide using a Site backup method, and importing to the new cloud site with the portfolio application in place, and you should be good to go…

Hello Mirco, To add a story to an Epic or adding an Epic to an Initiative from the scope view, select the issue that you want to link to the next hierarchy level up, to expand the details view for that issue and link it by setting the parent issue field with the desired parent issue: Alternatively contingent on the current…

Hi Megan, Thanks for the screenshot and it looks like you are using a Next-Gen project type, but currently Portfolio for Jira doesn’t support the next-gen project type and issue assignment to teams will not work on next-gen. You will need to use a classic project template to interface with portfolio at this time. Some…

HI Lindsay, Scheduling unestimated issues is covered at the following link for Jira Server 3.7 but note that there are some differences between the Live plan view, which is currently what is avaliable in Jira cloud, and this does not apply to the new planning experience, where Live plans and the new experience are both…

Hi Jeffrey, Thanks for bringing this one up, and great find. I see what you are talking about, but its not the Jira Filter Results gadget directly, it's the ORDER BY clause that is defining this order, and you will get the same behavior in the issue navigator when ordering by a text field. I created the following Bug…

Hi Austin, The Next-Gen project type uses The new Jira issue view settings for displaying the data, and there is currently a Bug in the new issue view causing it to not adhere to the global date and time settings that we are tracking at the following link, make sure to add yourself as a watcher to get an update when the…

Hi Balu, This is happening on a User role limit in the Postgres database settings directly, we have the following KB article that goes into a bit more detail but the fix is to set the connection limit to -1 for unlimited connections: * 'FATAL too many connections' error when using PostgreSQL database due to user-specific…

Hi Gabriel, The estimates on the Portfolio plan are not portfolio specific, Estimate assigned to the issue. Depending on your estimation unit, you'll see one or the other of the following: * Story Points * Estimates (h) * Estimates (d) When using "Estimates (d)" this is going to be tied to the "Remaining Estimate" field of…

Hi Janene, The target Start and end dates are a method to set a projected possible time frame that is used as a place holder to try and align the actual estimates and requirements during the calculations with what you want to have as the outcome. They are intended to be entered manually and not sync with the calculation to…

Hi Viktar, The attachment cannot be imported because the URL is not publicly accessible when using a hosted location for the attachment URL the file is on a system that cannot be accessed by the destination system (exe: it requires a login to access the image) When you upload to your files to the new server…

HI Mittapalli, Unfortunately on Jira Cloud you can't surface Target start and end fields directly in the JIRA issue screens. These fields are mostly intended to assist Portfolio users in roughly estimate and baseline the work on an issue inside Portfolio, However we recently introduced this on the Server platform and…

Hi Felix, Looking at the screenshot you uploaded the Hierarchy items are on the left and details on configuring the hierarchy can be seen here, and the timeline or schedule is on the right, and the bars in the schedule are based on the "Target Start" and "Target End" fields: For the Timeline, this displays issues in…

Hi Michael, At this time it is not possible, but this is something that is coming. In a classic project you can use Advanced workflow configurations to restrict how a transition can be executed, the function you would be looking for would be a condition or validator restricting the transition to a specific user group…

Hi Tobias, The H2 Database is highly volatile as susceptible to corruption as it is an in memory database, and any hiccup in the memory can completely cripple the data, which is why H2 is only recommended to front end system evaluation only. When errors occur on a H2 database the best course of action is to delete the…

Hi Rishika, This error looks like a project level permission error, you will want to log in as a Global Administrator (user with Administer Jira Global Permission) and then navigate to the projects "project settings" page and grant access to the project via the "Administer project" permission to the user as covered in…

I do love a good cuppa joe. Its a great pick me up in the morning, a good addition to any meal, and tastes great too, when done right. And there are soo many different blends and combinations of blends to preparation methods in the ways to do a cup of coffee from drip to espresso, pour-over to cowboy coffee, that the…

Hello, The Portfolio New Experience has moved away from the report structure that was a avaliable in the Live Plan interface (Covered here) which is no longer avaliable in the new view, in favor of sharable read-only versions of the roadmap as part of the changes in the new experience from the live plans as covered here: *…

Hi Calvin, At this time no, the New planning experience is only avaliable in Jira Server. However, this is discussed in a bit more detail in the comments on the following Portfolio 3.0 announcement discussion for the release of the Server/DC platform Versions, but we do have some major upcoming changes for the cloud…

Hi Ralf, Portfolio is going to attempt to schedule as much work as a user can complete based on the scheduling factors input for the user and issues. Described in more detail at the following links, noting one is for server and one is for cloud, but the two docs describe the same behavior in alternate ways and I recomend…

Hi Ralf, The earliest start date option was removed in the new experience view for portfolio, some of the details on how the scheduling is rearranged in favor of target start and end dates can be seen here: * Changes in the improved interface And if the "earliest start date" is required for your processes I would recomend…