Earl McCutcheon Atlassian Team

Hi Trish, Thanks for reaching out, and pointing this out. I think the jqlTooComplex is a red herring and possible false positive here and unrelated to the edit directly, I'm still trying to track that particular error down but I am not able to reproduce it locally in my tests so far, but looks very similar to the behavior…

Hi Lester, Thanks for reaching out about the post getting flagged as spam. We manually review all the requests that get flagged as spam to make sure there are no false positives caught in the filter, and it looks like the question was already removed from the spam filter so you're all set. But digging into the cause of…

Hello, Currently it is not possible to change the system date and time settings on a Per project basis, and we have the following feature request (both cloud and server respectively) tracking interest in adding this in as an option: * https://jira.atlassian.com/browse/JRASERVER-39511 *…

Hello Steven, Currently it is not possible to rearrange the order other than by changing the sort by Epic and Label when using a board on next-gen projects. We are tracking this at the following feature requests, make sure to add a vote to help us track interest for prioritization:…

Hey Rob, I would be happy to take a look, can you please provide some details on what you are seeing vs what you are expecting to see on the plan. Also If possible screenshots to go along with the explanations go a long way to help out so we can see what you are seeing. Regards, Earl

Hello Nghia, Thanks for reaching out to the community and welcome. To get a better view on the issues in a particular release you can use the Plan's filter options to show only issues in the cross project release. When setting the filter the cross project releases will be categorized under a header for easy identification,…

Hi Gil, A commit finalizes that the values and sets them on the issue. Once you commit a value to the sprint field the sprint is set and as you noted needs to be cleared to make changes to the plan as the scheduling algorithm is using the sprint field as one of the weighted items to calculate the issues position in the…

Hello Balu, Natively Jira stores the worklog on the issue and does not put together a list of the information per user, so the sum of the worklog not a directly queryable data point meaning it must be retrieved across all the issues and calculated manually from the avaliable data set. There is a really good exe on how to…

Hi James, Thanks for reaching out and that is an interesting idea, but as you noted "a classic case of not quite wanting either of two mutually exclusive alternatives" makes it a highly complex design to try to implement as its going to against the base design principles of how a project is structured. Fundamentally, Jira…

Hi Eloi, Thanks for reaching out and first to act as a referance point the Security Advisory Workaround is posted here: * Workaround for CVE-2019-15001 I recomend doing a quick double check on the syntax to verify it lines up with the KB, and verify that the file permissions were not altered in some way when editing, on…

Hello Essam, First off the permissions set for "atlassian-addons-project-access" are set by default. They are not intended to be changed, and should not be altered in any way as they are a special system group that give apps from the marketplace an elevated permission set in the background required by the apps to complete…

Hi Anna, Portfolio is designed to be a forward looking tool to tell you what you still can do vs a reporting tool on what you have done. And when you run issue import that occurs during the update to the issue sources it sets the baseline to that point to the most recent starting variable, and does not by default look at…

Hi Frans, Thanks for reaching out to the community, and with the new "Jira Cloud for Sheets" integration you pull the data across using Jira Query language (JQL) and overall you can get as elaborate as you want using these data import options, but there is going to be a lot of cross over with Jira JQL and the needed…

Hi Keir, Since the field is being set via the post function and required this is where the conflict is occuring. Basically the field on create has no value initially as the issue is being created it runs the validators first then the post functions. The validator triggers the popup to get a value entered, then after the…

Hi Kara, The use case you noted sounds like it would be a perfect fit to use initiatives for the company-wide OKRs. Depending on what you are looking to set up Themes may be more of what you are looking for, and I recomend checking out the following Blog post that goes into more detail on the intended use case for the…

Hello Jesse, Jira Portfolio does not support mapping workflow statuses to stages, that's a really interesting idea, though. Right now, the only way that you can mark a stage as "done" is if you set the estimate on that particular stage to 0, that signifies that no work is required for that stage. That's obviously a manual…

Hello Keir, Looking at the screenshot you added it is showing the "Team" field is set to required but has a value of "None", meaning a NULL value. As there is not a value set the create screen will pop up to prompt for input on the value. On Jira cloud a required field is set on the create screen in the workflow via a…

HI Gabriel, Yes, as you suspected the attachments need to be hosted and externally visible to be accessible by the Jira instance to be able to import the attachment. Post import the Images no longer need to be hosted externally as the images are copied to the new location on the Jira instance. Additional details can be…

Hi David, Overall I am not aware of any conflicts or bugs directly in this upgrade path, other than the best practices during a upgrade like checking for compatibility, and as you noted you already did a add-on compatibility check and it looked good, so just the general upgrade prep steps would be recommended, and I would…

Hi Ana, Thanks for reaching out to the community and welcome. As for the permissions to set up the initiatives hierarchy levels, It's the Portfolio Administrator global permission you need from the article you linked but there is a bug currently where the menu options are hidden behind the Jira Administrator permission.…

Hi Joshua, Check out the following Bug report for this behavior, but its pointed out in the comments that this only seems to occur on system GIT, and embedded GIT corrects the issue: I find that this behavior is issued only if I use system git (right now I have 2.21.0). If I switch to embedded git (2.20.1) and restart…

Hi Nina, Thanks for reaching out, in the Live plan view (2.X versions) the dependency values would alter the order when you calculated to update the scheduling algorithm post change (Details on how the algorithm was weighted in live plans here), and in the new planning experience, the dependencies will be flagged in the…

Hello, Thanks for reaching out and to address your last question first "Can this easily be done with using JSD?" Yes this would be really easy to configure using Jira Service Desk, as the Service desk projects are designed for this exact scenarion. With something like the default Request fulfillment workflow that looks…

Hello again Jesse, In addition to my comment above, as you noted being new to all the things Jira product related, I wanted to make sure you have all the resources to get off to a great start. Atlassian has a ton of material avaliable that extends across all the products that is all publicly visible, so the good news is if…

Hello Anjelika, When an Initiative shows up in the incorrect level in the schedule it usually indicates that one or more of the source projects that are set as an issue source are coming from a Next-Gen project, as currently Portfolio is only compatible with the Classic project types, and the parent child issue mappings…

Hi Jesse, We have the following Migration Hub Document that goes into a bit more detail on the differences in the application versions, that came out when we originally split Jira from one application into three for specific use cases, to highlight the changes that occure, and how the functionality differes based on the…

Hello Dhavval, There is currently not an option in the mail handler directly to accomplish this, its settings are currently designed to create issues and add comments via e-mail in the same setting. However, there is a workaround using automation rules in service desk, Check out the following KB article we have that…

Hi Chris, The easiest solution is on the system front end where you can generate a "excel view" export of the "Time Tracking Report" by going to the Project > Reports > Time Tracking Report, input the desired version to generate the report and select "Excel View" to download the data which can be opened in a spreadsheet…

Hi Tony, Thanks for the follow up, and CORS errors are not that common in JIra cloud outside API calls, and I just want to verify that your following the below set up process, as I was testing this one out and could not trigger the error: * Atlassian Cloud: Two-step verification Next, too narrow this down a bit further a…

Hi Dan, The plan is going to include issues from the issue sources by either Project, Filter, or Board, so looking at how issues are tied to these items would be the method of moving to a new plan. Noting using a Board as the source is the only way to include sprint data in a plan. So looking at a project, you can directly…