Earl McCutcheon Atlassian Team

Hi Natasha, I was playing around with the settings a bit and figured out where the disconnect is occuring. It looks like you have the Standard issue type that is the parent of the sub-task issues mapped to the Epic level here: Because the parent Story issue type is mapped to the Epic level and the Subtask cannot be…

HI Oupa, When you are selecting the board drop down during the issue sources association, is the board possibly further down on the list that what is rendering? Can you try using the scroll option to see the boards below the initial list of names that is rendered. Regards, Earl

Hi Cathy There is not currently an an option to set hours/availability for individuals users. First point I would like to address is that Capacity in the 3.0+ new experience is currently visible on a per-team basis as you noted and covered on the changes in the new experience article you linked. However this is an area we…

Hi Matt, Yes, the data portfolio side should be reflecting what you are setting Jira side, but some operations require a calculation to fully update. When you commit data in Portfolio you are verifying a write operation to jira and when you view a Live plan in Portfolio portfolio you're asking for a read from Jria's live…

Hello Marynel, The colors can be set using the "View Settings" drop down: Check out the Documenttaion "Customizing view settings" for more details on the setting. Regards, Earl

Hi Simon, Working in a next-gen project adding an existing issue to an epic is done from the backlog view using the 3 dot meatball menu dropdown to the right of an issue and selecting Add to parent, like this: This will trigger a popup allowing you to add the issue to the desired parent epic: If the Epic does not have a…

Hi Melissa, there is not a native JQL to search for comments by a specific user, and you would want to look into an add-on with extended JQL functionality to do this in JQL directly, a workaround used by many is to use the activity stream gadget on a dashboard for the desired users updates as described here. There are a…

Hello, To get all the story issues in a project you can use JQL in combination with the JQL API search function covered here: * Search for issues using JQL (GET) And then use a JQL statement like: project="ExampleProject" AND issuetype=story This GET would convert the JQL in the URL for the API endpoint for a curl command…

Hi Patrick, While i'm not entirely sure how this was triggered in your case we have seen this type of field duplication on the agile fields before, and it usually coincides with a recent upgrade triggering the duplication on the fields, have you done an upgrade recently that might line up with this. Also what version are…

Hi Natasha, Thanks for the confirmation and the issues would be well within the limits with 300, so there are a few other things to check. Please refer to the following thread that notes a really good list of items that could influence the visibility of issues in a plan: *…

Hi Adolfo, Other than the alternate suggestions and the Add-on I mentioned previously, I am not finding anything that would do something similar. However, we have the following feature requests tracking interest in a Read/Unread flagging feature for indicating issues that have not yet been viewed or have been updated that…

HI Natasha, You might be hitting a render limit on the number of issue present. How many issues are there in the issue sources for the plan? As covered in the feature request we have to increase these limits: * https://jira.atlassian.com/browse/JPOCLOUD-1671 Currently there is an upper limit of 100 Project and 5000 open…

HI Will; Ordering by Rank ASC is a requirement for the drag&drop to work on your board, if you define a static value to order by you cannot use the dynamic ranking options in parallel. It's an Either/or scenarion in this case. An options you can leverage to better manage priorities is to set up quick filters for the…

HI Jeff, As you discovered, Portfolio is going to take the value of the field when is manually set at the story level and pass that info back to jira, but the story point fields will show the estimated roll up value from the child subtasks. Portfolio interfacing with and is adhering to the methodologies set in Jira. This…

Hi Rodrigo, Currently the ability to disable a user is only available in the UI under user management, however this is coming soon, we are tracking the release at the following link noting the request is currently set to "Waiting for release" and we do not have a ETA on when that will be finalized but it is coming down the…

HI Matt, I wish I had something you could use right away, but on this one we just have to wait a bit longer, and happy I could help. Regards, Earl

Hey Aliaksandr, That error lines up with the one at the following Bug report, except the known Bug relates to special characters and not attachments or color formatting: * https://jira.atlassian.com/browse/JRACLOUD-70865 I did a few tests locally and I was not able to trigger either of the errors you noted using a…

Hi there, I have an addendum to add to Jacks comment as well, While you can do a project migration Service Desk to another installation and the issues will come across, there is currently an issue where the service desk specific AO database tables containing the Service desk configuration and SLA history items as well as…

Hi Bernd, The Hierarchy path of EPIC-> STORY -> SUB-Task is a set and default hierarchy path configuration defined by Jira and cannot be changed without add-ons. You can add in levels above the Epic called Initiatives, additional details on the default levels and Inatitive configuration ca be seen here: * Configuring…

Hi Deepak, Thanks for the confirmation, and since it's on the correct screen this means we gotta track down the "Unknown" portion of the error. Generally when this error occurs and is not related to the screen it's going to be either a permission conflict or a syntax related error in the call. First and this is a quick…

Hi Eli, To Automatically assign the sub-task to the parent issues assignee you will need an add-on to handle the logic. A few options for this: You could look into JIRA Misc Workflow Extensions as discussed in This post: *…

Hi Adolfo, There are a few different approaches you could take here, and some examples would be first and sounding like it aligns the most with what you're looking for would be the add-on In-App & Desktop Notifications for Jira that triggers popups for new issues either in app or via a desktop popup. Alternatively the…

Hi Matt, Check out the following Developer Blog on this topic that goes into more detail on this: * Jira Cloud next-gen projects and the effects on the REST API But as covered in the blog: There is no public REST API available to create project-scoped entities I would recomend watching This Feature Request for updates…

Hi Aliaksandr, Thanks for reaching out, and I would love to take a closer look at the behavior you're describing, and this does sound like there is some room for improvement or possible bug. First do you have the syntax of the error you encountered or know how to reproduce it? Screenshots would be helpful if you can grab…

HI Antun, The formatting notations for the classic markup views can be found at https://YOUR_URL.atlassian.net/secure/WikiRendererHelpAction.jspa?section=all However in the New editor and the editing view used in Next-gen Projects, is moving away from using wiki style markup to a WYSIWYG editing approach, using Quick add…

Hi Kitty, There is not any options that I am aware of that can accomplish counting the number of labels on an issue in Jira cloud nore are there any add-ons that I am aware of in cloud that can do this, there is an add-on related workaround for Jira Server detailed 'At this link', but again nothing I can locate for Cloud…

Hey Duc, Happy to help, and I have already passed along the feedback to the dev team, but another avenue you have to get some additional feedback going around this is to drop a comment on the following discussion that our Jira Cloud PM just added earlier today. * Calling all Jira Cloud users! Give us feedback on our…

Hi Andrew, The default time tracking options in Jira are going to targeted at Issue based time logging not the user based time tracking. So it's geared to look at project to issue relations not the issue to user relations for a project level work logs. You might be able to leverage some of the capabilities of the User…

Hi Eric, We have a really good breakdown on the changes to the new interface and the difference between the live plans compared to the new version that can be fond At this link. We are always looking to make the new experience line up with feedback from end users to make the system better, Make sure to look through…

Hi Duc, Issue security in the comments is a feature that is not yet available in the new issue view, we are tracking interest for prioritization efforts to add in the feature to the new issue view at the following future request, make sure to add your vote to help with the prioritization efforts: *…