Earl McCutcheon Atlassian Team

Hello Saldy, The Earliest Start date and the Target Dates are manually entered items, and removing them can be done by selecting the field and deleting the value, or modifying the value to a new entry. Noting You can add Target dates to an issue the Earliest Start Date field is only available in Portfolio and not able to…

Hi Vincent, Looking into this a bit I found this post on the Oracle forum with a note from the Oracle XE product Manager: There is no Oracle 12c Express Edition (and there will be no 12c XE). And it looks like 12c xe was replaced by 18c per This Blog post As this pertains to Jira 7.13 & 8.0, Oracle 12c R1 is the only…

Hi Randy, You already noted Point 3 is covered by the issue security levels and point 1 and 2 can be covered with Project Permissions. The following KB details how to set this up: * How to limit user to only browse issues assigned to or reported by them Regards, Earl

Hi Peter, There is a bit of a gap in the documentation currently: * Advanced searching - developer reference And the Doc update is being tracked at the following request that contains details on the additional functionality, and available query options missing from the main doc: *…

Hello Veerle, The Next Gen Projects do not yet have Sprint Reports Included, the following Feature Request is tracking the features implementation: * https://jira.atlassian.com/browse/JSWCLOUD-17208 And the following Page is tracking the primary focus upcoming features in Next Gen projects: *…

Hello Martin, This is covered in detail in our licensing FAQ at the following sections: * https://www.atlassian.com/licensing/purchase-licensing#payments&refunds-6 * https://www.atlassian.com/licensing/purchase-licensing#upgradingserverlicenses-2 But Ultimately just reach out to the Customer Advocates team…

Hello Helen, When Creating the Database, you need to create all the tables empty, with the correct table & column collation, and it sounds like there is a mismatch between theses from the previous modification, i.e. either the tables reflect the supported collation, but not their columns or vice versa. Please refer to this…

Hi Ram, I broke out each of your questions below to make sure I did not miss any: When a plan is created by adding only epics AND excluding all JIRAs without epics, any new JIRA gets automatically added to the plan. Even when that new JIRA is not part of any included epics. This is super frustrating. We would need to…

Hi Dennis, Eazy BI and all in one reports for Jira, are two add-on apps that I know have various customizable bar charts similar to what you noted. I would recommend checking these two out as well as browsing through the other apps at the following link to see if there are any others that would better fit your needs: *…

Hi Adam, Currently no, you cannot link skills and stages to components, but please add a vote to the following feature request to add this function into portfolio: * https://jira.atlassian.com/browse/JPOSERVER-1820 Also if you have any additional feedback on the functionality please drop a comment detailing your use case…

Hi Sneha, Check out this Feature request, and make sure to add your vote: * https://jira.atlassian.com/browse/JSWSERVER-3573 But currently you cannot transition an issue vertically in the same column, the workaround is to select the desired issue then use the period key "." to open up up the options menu and select the…

Hello Aleksandra, First thing I believe would help you out, but unfortunatly is not available at this time is the following feature request to add in a per issue type max assignee value that would allow for the GFX issue type to be set as a single assignee where other issue types could be set at higher levels, make sure to…

Hello Bipin, In Portfolio the selected releases on a plan is to suggest releases you can work with, if you have only selected "Version4.0" this indicates any issue flagged in that release as well as any issue that does not have a release so that it may be planned into that release. By Selecting a single release it will…

Hello Reji, Check out this previous post for a referance point that contains a great list of items that could cause issues to not display in a plan: * https://community.atlassian.com/t5/Jira-questions/Issues-not-showing-up-in-Portfolio-Live-Plans/qaq-p/108507 I would suspect that the epic has either been excluded from the…

Hi Oliver, Check out this Documentation for a referance point: * Assigning issues to sprints And from what you have noted it sounds like you are running int a conflict on the point in the Doc under the section "How to assign issues to sprints from the timeline", most likely the estimate, or the sprints existence in the…

Hi Richard, Check out the product demo pages here: * Portfolio * Jira Software * Jira Service Desk Regards, Earl

Hi Cassandra, You could do this with the Workflow Property "jira.permission.work = false" set on the 'Done' Status Check out the following guide from j-tricks which has a really good breakdown of the functionality, that goes a bit deeper into the functionality: *…

Hi Lonneke, First I have a few questions for clarification. Are you on Cloud or Server, and does the dashboard that is failing to show the slideshow have Agile specific Gadgets (like Sprint Burndown, Agile Wallboard, Version Report, or Sprint Health)? If you're on Jira Cloud I believe you are hitting the following BUG…

Hi Andrea, Portfolio is designed as a forward looking application and is generally configured to ignore past and completed work items as they are not necessary to define a schedule of what still need to be done over what has been completed unless the allocated range is expanded to include these items. From what you have…

Hello Christian, In this specific scenario referring to the documentation for the Jira native JQL functions and then the Documentation for any of the third party applications you have installed for a list and description of the functions would be your best bet, as the JQL is not a value stored as an item that lives in the…

Hi Benjamin, In Jira Standalone directly, no, the integrated Crowd directory on a Jira Standalone installation cannot integrate with google at this time, but a separate Crowd server does have an integration option, as well as Third party SSO apps. Check out this Feature request with some details on the options available…

Hi Paula, Check your Jira logs for a message on API rate limit being exceeded it would show up as something like "Sync Failed: API Rate Limit Exceeded" If this is the case GitHub has a Rate limit of 5000 requests per hour and even though you only have 10 accounts there may be more than 5k requests attempting to Sync. As…

Hi Karim, Yes, Issue collectors can specify a reporter to use so that the form is submitted by that user on behalf of the anonymous user. There are two options that can be specified for matching the reporter covered in the Using the issue collector documentation: * Always use Issue Reporter — select this option to ensure…

Hi Ryan, Ultimately I would recommend not attempting doing this as it really takes away the agile nature of an agile board, Where Agile methodology is all about prioritizing work items but applying that work in a non ridged manner for dealing with change in a development cycle avoiding limited restrictions in place. While…

Hi Michael, All the permissions for access to the KB content is going to be dependent on the Confluence side via Global permissions , Space permissions & Page restrictions. but as for restricting permissions to knowledge base spaces its an all or nothing link, you can only allow your customers access or not, and there is a…

Hi Lara, Thanks for bringing this up and that is a great find with a clear use case for a Bug, so I created the following Bug Report to track progress on a fix: * https://jira.atlassian.com/browse/JRASERVER-68905 If you have any additional feedback please feel free to drop a comment on the Bug report, and add yourself as a…

Hello Charles, I believe to achieve what you are looking for you would need to have the automation rule trigger a transition and then on the workflow use something like what is described In this post or this post or this post to set the field value via a scripted post function during the issue transition. In the automation…

Hello, Thanks for the info and the Plugins noted are bundled system plugins and are not stored in the installed-plugins directory under your jira home but rather the Jira install directory at "$Jira-Install/atlassian-jira/WEB-INF/atlassian-bundled-plugins", and loaded from the various .jar packages. Check the permissions…

Hello Ashley, The Epic Issue type is designed to work in a Jira Software Project type as an Agile issue type, and the Agile related field types that make up the Epic (Epic Name, Epic Link, Epic Status, Epic Color) are also not intended to be used in a Core/Business project, but rather in a Software project in a Scrum or…

Hello Ran, That behavior is noted in the Portfolio for Jira FAQ for Classic plans and as noted in the header: This page refers to Portfolio classic plans. If you're using Portfolio 2.0 and later, please check this section for frequently asked questions about Portfolio live plans. But for Live plans in Portfolio 2.0 and…