Earl McCutcheon Atlassian Team

Hi @Dipak Naokar , I'd be Happy to take a look, and I am covering a lot of information so I broke your comments out into sections to make sure I covered all the points. I am pretty sure I got it all but let me know if I missed something. On the comment you had about how Bugs are handled: I have seen the documents and…

Hi @staceyking , Good question and Yes, the same logic will apply to Jira Cloud Projects linked to a Portfolio plan as well when dealing with cross project plan vs project focused plans. The Portfolio documentation is structured slightly differently for the pages relating to Server and Cloud, as there are some difference…

Hi @victoria.mcguire , Thanks for reaching out, and welcome to the community, and your current setup using the classic plans is the optimal configuration for Portfolio. Currently in Portfolio the plans are designed to be compatible with the Classic projects, and with next-gen projects are not compatible on many of the…

Hello @Jens Vanpachtenbeke , The functionality you are looking for in a collaborative shared custom view (filters/view settings/columns etc) as a working plan, is something that is currently on our radar for implementation, but not yet avaliable. Currently the plan can be worked on in tandem by users with edit permissions…

Hello @douglas.estabilis , It sounds like you are missing a permission allowing you access to the portal as a customer, check out the following Documentation for what items to check: * Managing access to your service desk * Customizing Jira Service Desk permissions Alternatively this behavior can be caused by a change…

Hello @Adrian_Munther , Thank you for pointing this one out, and it is definitely missing from the UI and looks like a new BUG in the 4.6.X versions. I created the following Bug Report so we can follow up on this and get a fix in place. * https://jira.atlassian.com/browse/JSDSERVER-6727 Please add yourself as a watcher on…

Hi @[deleted] , The Archive functionality as noted in the "Managing versions" is designed to be a semi transparent view into the old versions when flagged as archived, and the intended functionality is to hide an old version from the Change Log and reports to avoid the added noise in the Jira User Interface. The Feature is…

Hello @justmark , Thanks for reaching out, and as you mentioned the process of Adding the initiatives as a separate project is the recommended process when you are working cross project initiatives, but is not recommended in scenarios where you only need additional levels within projects individually as covered in…

Hello @Ezop_Idea , The functionality is not avaliable in that version of Jira Service Desk, As covered in the related feature request for this functionality: * https://jira.atlassian.com/browse/JRASERVER-62457 You will want to upgrade to Jira Server 7.13.1 / Service Desk 3.16.1 version or later to export the SLA details.…

Hey @Erick Johanson , I was not able to find anything published on the documentation sites for the parent link, but I was able to reach out to a few members of the Adaptavist team (the vendors for the add-on ScriptRunner) and they offered the following snippet as a way to link Epic to the parent initiative through the…

Hello @hitesh kumar dewangan , Thanks for reaching out and restating the goal and problem statement, you are trying to migrate Issues from 'cloud A' to 'cloud B' using CSV import, but you are having an issue with the authentication. For the user authentication information in the CSV you want to use a user with access to…

Hello @Isabelle Tot , Currently the Core Boards used by the Business Project type do not display the Subtasks in the board. To get this functionality you would want to look into a Jira Software project type and the Swimlane capabilities of the board configurations on Software Projects. Also, we have the following Feature…

Hello @Batata Saeed , Thanks for reaching out, and to escape the characters that are being converted to emojis in your API posts there are a few options. First if you switch to use the New Jira Issue View , the system now uses a Markdown editor instead fo the Markup editor used in the classic view and the auto conversion…

Hi @Jonas Maier , The Print Card feature is controlled by one of the system plugins in the .osgi-plugins directory: $jira-home/plugins/.osgi-plugins/transformed-plugins/jira-greenhopper-plugin-<VERSION_NUMBER>.jar via the 'gh.cardprinting.*' elements, in the various files contained in the JAR file. And I believe all the…

Only problem is, I can't remember what I've forgotten!!!!!!!!

Hi @Tim Peters , It sounds like you have the Approvers field added to either the Edit or View Screen allowing it to be modified ad-hoc, and when an issue is edited it triggers a Update event to process the notifications, but the approver notification is sent when the issue is transitioned into an approval status, and…

Hi @nph , Sorry for the delayed reply, but looking at this the menue options for the applications should be using the same base URL as the main application, so navigating through Jira should have the same behavior as navigating through installed apps. I am wondering if there is something in your DNS or Proxy settings doing…

Hello Adam, I am Familiar with the Jira Cloud for Sheets add-on but not so much for the Google Sheets Integration (by MobilityStream, LLC), and I only have a referance from the docs for the comparison. So, I can fill you in with details I am aware of for difference Jira Cloud for Sheets Add-on based on what is listed on…

Hello @Ihor Barinov , Thanks for providing the console details, and checking out the error: 'Unchecked runtime.lastError: The message port closed before a response was received' I found several hits on various forums indicating that the error you are seeing is most likely related to a browser extension causing the failure…

Hello @Kenny Nguyen , Currently only story point estimation is avaliable in Next-Gen projects and Time Tracking estimates are still in the works as an upcoming feature, so the aggregate / summation fields signified with the "Σ <Time Tracking Field Name>" such as the "Σ Original Estimate" and "Σ Remaining Estimate" fields…

Hello @cherdsit_t , Thanks for reaching out, and looking at the screenshot and the details you provided I think the conflict might be on Jira API vs Service Desk API for create issue options. First you have this question flagged with a jira-service-desk-cloud tag, which is where I am pulling this assumption from so please…

Hello @Yuval Zaltz , We have the following Knowledge base article detailing the steps on how to change the default logging locations, check it out and let me know how it goes: * How to change the location of stdout and stderr logs Regards, Earl

Hello @ilker isler , Jira does not have a concept for start and end of a project, but rather allows for setting goals within the projects issues, or releases. The project itself starts when created and ends when you remove access to the project so that no users can create or edit issues within that project. You can however…

HI @mike.larma , After removing issues from a plan by explicitly flagging them for removal, you can add them back in by editing the issue sources, and any issue that was flagged for removal will be displayed on the "Confirm what's in scope" screen with the checkbox deselected: Reselect the issue to add it back to the…

Hello @Fabienne Pagnier , There is not a way to combine the two separate plans into a single plan without modifying the plan sources. The plan Sources are basically a filter restricting the data displayed in the plan to only the content selected in the source. Currently there is a Feature that would help you out here but…

Hi @matt.lightbourn , I can step in for Daniel, for the follow up question. Overall The atlassian suite of products will have a broad set of features but offer third parties the ability to customize the application via add-ons to specialize the application for specific use cases not met by native toolsets. When it coms to…

HI @femosso , Happy to help, and I was doing some more digging on this one to see If i could locate a better solution that fit your use case, and found the following Feature request that I recomend adding a vote to to help us track interest in for implementation as I believe this would really help you out by providing a…

Hi @Nichola Tolmie , There are a few variables that could cause issues to not be displayed on the plan, I would recomend checking out the following Post where there is a really good checklist of items mentioned in a comment by my associate Martin Suntinger for a quick run through as a starting point: *…

Hello @Gabriel Oliveira , If your trying to pull the email from the assignee field of an issue, I believe you should be able to do a "GET /rest/api/3/issue/{issueIdOrKey}" and expand by adding a "?fields=assignee" to see the email address for the assignee field of that issues. Try in this format and let me know if this is…

Hi @femosso , First as a referance point for the follow up info the full documentation on the JQL filter operations can be found at the following documentation page and its sub pages: * Advanced searching And as you noted there is not an option to only apply a modifier by itself as the quick filters are sefl contained full…