Earl McCutcheon Atlassian Team

Hey There, It sound s like you are missing the Shared team management permission as covered in Permissions in Portfolio for Jira

Hello Daniel, Check out the Portfolio permissions Documentation below for a reference point: - https://confluence.atlassian.com/jiraportfolioserver/permissions-in-portfolio-for-jira-934719058.html To see portfolio plans the users needs global Portfolio view permissions or Edit permissions if you want them to also make…

Hi Lucca, I sent some info your way on another community post you filed on this that looks like a duplicate of this one, but we wanted to make sure the info was in both locations, we were able to reproduce and verify that this is tied to the radio button custom field type and we are tracking the bug here:…

Hi Lucca, We just tacked this issue down to Radio Button Custom Field types added to the plan, and created a bug report for it here: - https://jira.atlassian.com/browse/JPOSERVER-2365 Regards, Earl

Hello Darya, The share option currently does not have a history tracking method, and we are tracking this as a feature Request here: * https://jira.atlassian.com/browse/JRASERVER-32125 Make sure to add your vote to help us with prioritization efforts. As an alternative, I would recommend looking into a third part…

Hello Alaa, At this time it is not possible the SLA metrics and calendar options need to be manually configured per project. We have the following Feature Request to implement this: * https://jira.atlassian.com/browse/JSDSERVER-191 Please make sure to add your vote to the request as covered in the Implementation of New…

Hello, A Circular Dependency happens when an issue effectively blocks itself on a Logic conflict. The most basic scenario occurs when an issue is blocked by and blocks the same issue. But a more complex scenario is: * issue ABC-1 blocks ABC-2, and ABC-2 blocks ABC-3 * ABC-1 must be complete before ABC-2, and ABC-2 before…

Hi Urszula, The "AjaxIssueEditAction" is not much to go on by itself but the full console error would help narrow this down a bit further, such as if there is an error code associated with the action, or what is being called when the error occured. But Some additional checks to run here to narrow this down: * Is anything…

Hi Brian, I Believe the formatting you are looking for is a quad backslash "\\\\" . Check out this previous community post with a similar scenario: * Script Runner - Description formatting -Earl

Hello Srinivas, The Application access is governed by a group associated to application access, in a scripted create if you have the the default group membership for new users in jira set to a group with application access then the user should be added to this group on create. This is done under Admin >> Applications >>…

Hello Darko, If you do not want to use the existing WhiteSource Intergration for Jira App, You are going to need to develop your own custom app for the intigration. To get started on this I would suggest looking at Developer Documentation which has various guides and examples on creating plugins and intigrations: *…

Hi Brett, That is correct and by Design, Issues that do not have work to be done cannot be scheduled so they do not show up in the timeline or schedule view, and we have the following Feature requests that all tie together on this functionality: First and the most relevant to your specific concern: *…

Hello Mohamed, It sounds like Story B has been manually added to the same sprint that Story A is part of. And when Manual association is in place this overrides the calculation performed by portfolio. Check out the Scheduling Behavior Documentation for more details on this. -Earl

Hello Swarna, It sounds like you are running into this BUG: * https://jira.atlassian.com/browse/JRASERVER-33054 Please check this out and If this is the case the workaround is viewable in this KB article: * Some issue types are unavailable due to incompatible field configuration and/or workflow associations. -Earl

Hello Linda, Details on setting up Releases in Jira Portfolio can be found here: * Releases The page includes a demo video with the steps and example on the process. Alternatively the Versions can be created on the jira side and will be included into the plan, details on creating a Version for a release can be found here:…

Hello Aljoscha, Please check out This Previous Community Post, as this looks to be the same scenario, and has a very detailed explanation on the expected behavior for the Mentions. - Earl

Hello Marzi, Within Jira each issue individually has the History tab that can be used to view the changes that occur on the issues, but there is not a way to generate a in application Report on these items. However, you can use the Issue API and expand the Changelog of the issue which is the history of all changes of the…

Hi Dania, The Schedule designed to be forward-looking by default and show work that is still needed to be done. When an issue has a resolution set, it won't be visible in the Schedule anymore. But you can adjust the timeframe and status visibility to see completed issues. Additional details on this behavior can be seen in…

Hello Ron, Currently as you described, Portfolio can schedule Individual team members Availability, but does not have an option to Manage a full teams availability, the only option is to manage the users within the team individually. I created the Following Feature Request to track interest in this as a new feature…

Hello Manu, Details on customizing the login gadget can be found here: * How to customize the login gadget Noting this KB is formatted for jira 6.4 and earlier installation for step 3 in the files to alter, but the main details on kb are the unpacking and repackaging the file. The Error message you are looking for is…

Hey there Paul, It sounds like you are running into this BUG: * https://jira.atlassian.com/browse/JSDCLOUD-5671 Can you check this out and let us know if this is the case?

Hello Chris, The best guide I am aware of for Jira & Portfolio capabilities using SAFe can be found in the white paper that can be downloaded here: * https://www.atlassian.com/software/jira/portfolio/scaling-agile-with-safe The Guide notes using the Individual Sprint Reports to itemize the issues completed or not completed…

Hello Teresa, When Creating the Issue collector select either "Raise a Bug" or "Custom", and the "Rate this page" option with the emoji's will not be included on the template. Then for additional customization options check out the Advanced use of the JIRA issue collector documentation.

Hello Brendan, I know there are some conflicts in the create transition that I am aware of in portfolio covered in the following feature request relating to how portfolio temporarily stores data before committing, and you may be running into a similar result on your scripted listener: *…

Hello Luca, When you run into this error it usually indicates that you have data on an issue that is attempting to load which relies on code that is being provided by a third party add-on which is either in need of an update or erring in some way. I would recommend checking under the manage add-ons page for any installed…

Hello Stephen, Thank you for your comment and this comes down to the calculation requirements for un-estimated issues, overall this is not clearly defined in the Mapping issue assignees to team members documentation, so I put together the following Documentation update request to provide the required details.…

Hi Terrell, If you do Find out what is causing this or you can narrow this down and collect an error or steps to reproduce please do let us know, as this would be a valuable fix if this does turn out to be a bug.

Hi Terrell, Since this is failing but later on you are seeing these values show up after a few hours, the behavior is just screaming that there is a performance or indexing issue on Jira preventing the value from showing up immediately, but later on the action is able to complete or is getting triggered by another action…

Hello Amin, This is not available at this time in the JQL search options, we have the following Feature Request tracking the implementation: - https://jira.atlassian.com/browse/JPOSERVER-447

Hello Dima, The Scheduling behavior comes from a few different locations for the calculation, and is covered in mode detail here: - https://confluence.atlassian.com/jiraportfolioserver/scheduling-behavior-802170552.html The Placement of the issue in the timeline (Stretching across the timeline) is the calculated Scheduled…