Hi 69fc0c73693f,

I agree with you that 2016 is a long way in the past, but please allow me to share some history context.

Until mid 2020, our Team was heavily focused on developing Advanced Roadmaps in Server. Cloud only had a basic version back then, with less features than in Server.

When the end of support for Server products was announced (https://www.atlassian.com/migration) in June 2020, we started to migrate the most recent version of Advanced Roadmaps from Server to Cloud ~15 features of which, Export to CSV.

In 2021, we started working on two highly requested features: Edit issue description and Export to PNG, which we both released in March 2022 - if you missed the announcement, here it is: https://community.atlassian.com/t5/Advanced-Roadmaps-articles/Two-new-features-in-Advanced-Roadmaps-in-March/ba-p/1978764

It was also announced by 270122f7c34d on this feature request ticket that Export to PNG was available: https://support.atlassian.com/jira-software-cloud/docs/create-a-static-image-of-your-plan/

We could have posted a similar announcement, but we felt like it would have been a duplicate. Sorry for that.

The reason we kept this feature request open boils down to the fact that it also includes export to PDF. However as I stated before, we have no proper way of distinguishing who voted for one or the other, or both, hence the idea of closing this ticket and create another one specifically for export to PDF.

Best regards,

Quentin

Hi 311a7d4f9122,

I understand your frustration about the feature requests you posted, but none are related to Advanced Roadmaps unfortunately - we're one of many Jira products / Teams. Our Team only focuses on feature requests for Advanced Roadmaps

You can see the list of feature requests for Advanced Roadmaps, listed by the most votes here: https://jira.atlassian.com/issues/?jql=project%20%3D%20JSWCLOUD%20AND%20component%20%3D%20%22Plan%20(Advanced%20Roadmaps)%20-%20Roadmap%22%20AND%20type%20!%3D%20Bug%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20votes%20DESC

The point I am trying to make with my list is that we (Advanced Roadmaps Team) are watching constantly our list of feature tickets, and we action either the most requested ones either the easy, quick-win ones. Making some customers happy by picking up one feature request also means postponing / deprioritising other features and making other customers unhappy - there's a constant trade-off we have to make.

Coming back to this ticket though, I'll try and gather the amount of votes that were accumulated until the time the ticket was renamed from Export plan as PDF to Export plan as PDF or Image in January 2022.

• If the vote count is close to the current amount of votes on this ticket, I'll reopen this ticket and label it back to Export plan as PDF, to spare any confusions
• If the vote count is very low, I suggest using the new ticket https://jira.atlassian.com/browse/JSWCLOUD-25466 in which I will add the amount of votes for PDF export in the description, in order to have an accurate number.

Does this sound like a good compromise?

I am not trying to be difficult here, but it is crucial for us to know the exact amount of votes on a feature request. It helps us prioritising features based on the most requested ones.

I hope this all helps,

Quentin

I saw notifications more than SEVEN YEARS LATER about this request that Atlassian seems to have mostly ignored since then.  We moved away from Jira Portfolio a long ago because what's the point in doing a bunch of planning work on roadmaps if you can't share the roadmaps with anyone?  We made that decision after I posted here and the conclusion of my research was that Atlassian wasn't interested in making roadmaps shareable.

The sharing options in the new 'Advanced Roadmaps' feature seem comparable to Airfocus, so maybe we'll try that.  Maybe.  This was a weird way to learn about it that doesn't make Atlassian or that product look good.

Hi Quentin.. thanks for you answer.. 

i am not agree with you in any sense.. 

In first place, this ticket was originaly created as Export Plan as PDF, then you changed it as PNG / PDF.

if you read the comments, nobody ask for PNG, but for PDF.

Second, you can list a lots of work of Atlassian , an that is not a surprise, in fact Jira is a paid tool. so that is part of your product and what you sell... 

The surprise is the list that you dont see (see below). I don not why , maybe because you dont see the economic benefits o something but there are a lot of issues or sugestions that are open before several years.

Dark Mode was Created Nov 2016 (you resolved it +7 years later.)

This list is gathering interest or in (a far) future consideration

• https://jira.atlassian.com/browse/JSWCLOUD-17608 
  Add granular permissions relating to version control
  1284 votos
  Feb 2019  (+4 years and still open)
• https://jira.atlassian.com/browse/JSWCLOUD-14833
  Should be able to translate locked custom fields of JIRA Software
  102 votos
  Sep 2016 (7 years and still open)
• https://jira.atlassian.com/browse/JRACLOUD-37024
  Different column background-colors for different ticket status
  240 votes
  Feb 2014 (+9 years and still open)
• https://jira.atlassian.com/browse/JRACLOUD-15900
  As an Admin I want the ability to share the visibility of a filter with Groups and Roles that I am not a member of
  406 votes
  Nov 2008 (15 years and still open)
• https://jira.atlassian.com/browse/JRACLOUD-59932
  Separate license base for Addons
  707 votes
  Feb 2016 (+7 years and still open)
• https://jira.atlassian.com/browse/JRACLOUD-21936
  Allow nested JQL function calls
  525 votes
  Aug 2010 (13 years and still open)
• https://jira.atlassian.com/browse/JRACLOUD-69298
  Allow fields to be hidden when certain group or users views a ticket
  256 votes
  Apr 2018 (+5 years and still open)
• https://jira.atlassian.com/browse/JRACLOUD-6798
  Allow admins to translate items configurable in the administration section
  595 votes
  May 2005 (+18 years and still open)
• https://jira.atlassian.com/browse/JRACLOUD-28225
  Mentions of groups
  584 votes
  May 2012 (+11 years and still open) 
• https://jira.atlassian.com/browse/MIG-392
  CSV Importer produces errors when mapping the Issue Type field
  53 votes
  Jan 2018 (+5 years  and still open)

And this is only my short watching list.

Sorry if this is not the place. 

Best Regards.

Hi 311a7d4f9122,

Unfortunately, this ticket was labeled as Export to PNG / PDF, and we have no way to distinguish who voted for the PNG export and / or who voted for the PDF export.

We consider the amount of votes to prioritise feature requests. Out of 181 votes at the time of writing this ticket, unfortunately we don't know if exporting to PDF gathered 1, 10, or 150 votes.

Hence why I created another ticket - https://jira.atlassian.com/browse/JSWCLOUD-25466 to help us having a better representation of the vote count.

As for "we are used to Atlassian not doing what people ask for", this isn't entirely correct. Over the past year, we released (amongst other things):

• Dark mode (8000+ votes)
• Export to PNG (top 6 of JAC feature requests)
• Additional groupings and filters in the dependencies report (requested by 100+ customer feedbacks)
• Bulk edit labels (requested by 50+ customer feedbacks)
• Grouping by custom fields (top 4 of JAC feature requests)
• Creating labels from Advanced Roadmaps (top 20 of JAC feature requests)
• A new timeline header
• A new Jira-like navigation / layout
• Create a sample plan
• "Where is my issue?" A new feature to find out why issues are missing in the plan
• Clone a plan (requested by 80+ customer feedbacks)

And we're releasing soon:

• Team-managed projects support (1584 votes)
• Reporter field support (80+ votes)
• Issue status update from Advanced Roadmaps (234 votes)
• Jira Team platform support (309 votes)

This along with performance updates which, amongst other things, reduced plan load time by 50%.

I know it's never fast enough, but we're doing our very best within our Team capacities to ship what customers would like the most.

Best regards,

Quentin Feyaerts
Frontend Engineer at Atlassian

Dear Quentin, I don't think you can change the title and the description of this issue and close it like that.
All the votes that this item has, which was created in 2016, are lost...
If you do this to disguise "performance numbers" ok, we are used to Atlassian not doing what people ask for ,but it is not correct.
All the comments and all of us who voted for this issue did so because we need the PDF export functionality, and closing it seems to me to be a mockery of those of us who voted for this item and have followed it for years.