jira.atlassian.com Open in urlscan Pro
185.166.143.25  Public Scan

Form analysis
2 forms found in the DOM

GET /secure/QuickSearch.jspa

<form action="/secure/QuickSearch.jspa" method="get" id="quicksearch" class="aui-quicksearch dont-default-focus ajs-dirty-warning-exempt" role="search">
  <input id="quickSearchInput" autocomplete="off" class="search" type="text" title="Search ( Type '/' )" placeholder="Search" name="searchString" accesskey="q">
  <div class="quick-search-spinner"></div>
  <input type="submit" class="hidden" value="Search">
</form>

<form id="jira_request_timing_info" class="dont-default-focus">
  <fieldset class="parameters hidden">
    <input type="hidden" title="jira.request.start.millis" value="1698846149429">
    <input type="hidden" title="jira.request.server.time" value="108">
    <input type="hidden" title="jira.request.id" value="822x126816180x1">
    <input type="hidden" title="jira.session.expiry.time" value="-">
    <input type="hidden" title="jira.session.expiry.in.mins" value="-">
    <input id="jiraConcurrentRequests" type="hidden" name="jira.request.concurrent.requests" value="1">
    <input type="hidden" title="db.reads.time.in.ms" value="10">
    <input type="hidden" title="db.conns.time.in.ms" value="13">
  </fieldset>
</form>

Text Content

Log inSkip to main contentSkip to sidebar
Linked Applications
 * Atlassian Documentation
 * Atlassian Community
 * Atlassian Support
 * Atlassian Developers
 * Atlassian Marketplace
 * Billing & Licensing
 * Statuspage Jira
 * Advisory Services JIRA
 * Jira
 * Jira
 * Jira
 * Jira Platform Jira
 * Confluence
 * Ecosystem Confluence
 * Fisheye and Crucible
 * Bitbucket - {7ccca8ea-2abb-44b7-a3f8-8d901528979c}

 * Dashboards
   
 * Projects
   
 * Issues
   
   

 * 
 * Give feedback to Atlassian
 * Help
    * Jira Core help
    * Keyboard Shortcuts
    * About Jira
    * Jira Credits

 * Log In
   


JIRA CLOUD


 * Issues
 * Reports
 * Components


 1. Jira Cloud
 2. JRACLOUD-66843


WHEN EXPORTING TO CSV EPIC LINK SHOULD CONTAIN THE EPIC NAME AS IT DOES IN THE
ISSUE NAVIGATOR


Log In

Gathering Interest


Export

nullView workflow
XML
Word
Printable

DETAILS

 * Type: Suggestion
 * Resolution: Unresolved
 * Component/s: Jira - Site Export - To Server
 * Labels:
    * jsw-s5

 * UIS:
   36
 * Support reference count:
   26
 * Feedback Policy:
   
   Our product teams collect and evaluate feedback from a number of different
   sources. To learn more about how we use customer feedback in the planning
   process, check out our new feature policy.

DESCRIPTION


PROBLEM DEFINITION

On the issue search, the Epic Link column displays the Epic name. However, when
this query is exported to CSV, the Epic Link column displays the Epic Issue Key.






SUGGESTED SOLUTION

Allow the customer to export the query to CSV file as it is displayed on the
screen.


WHY THIS IS IMPORTANT

If this CSV file is used for another purpose than importing back to JIRA,
knowing the Epic Issue Key may not be useful.


WORKAROUND

Use the Print List option.

ATTACHMENTS



ATTACHMENTS

 * Options
    * Sort By Name
    * Sort By Date
   
    * Ascending
    * Descending
   
    * Thumbnails
    * List

 1. 
    Screen Shot 2017-05-05 at 10.26.15 AM.png110 kB05/May/2017 1:51 PM
 2. 
    Screen Shot 2017-05-05 at 10.49.27 AM.png70 kB05/May/2017 1:51 PM

ISSUE LINKS

is related to

JSWCLOUD-24152 Provide Epic Link Summary as an available Jira Cloud import data
field

 * Gathering Interest

mentioned in

Page Failed to load

ACTIVITY

[JRACLOUD-66843] When exporting to CSV Epic Link should contain the Epic Name as
it does in the issue navigator
 * All
 * Comments
 * Work Log
 * History
 * Activity

Newest first

Pieter Gruijters added a comment - 3 hours ago

Similar issue for Jira plug-in to import user story overview in excel - I used
to do manually by exporting HTML in Jira and open the file in excel (work's
cool). Here i have the EpicLink as description, but using the same filter in
Jira plug-in in excel I get the key of the epic instead. My report is messed up
now and automated refresh for the report will not give me the result as before
where I like to have the Epic displayed with text instead of JiraID. 

 


Pieter Gruijters added a comment - 3 hours ago Similar issue for Jira plug-in to
import user story overview in excel - I used to do manually by exporting HTML in
Jira and open the file in excel (work's cool). Here i have the EpicLink as
description, but using the same filter in Jira plug-in in excel I get the key of
the epic instead. My report is messed up now and automated refresh for the
report will not give me the result as before where I like to have the Epic
displayed with text instead of JiraID.   
Cayla Halliday added a comment - 28/Sep/2023 2:47 PM

My Team spends hours a month in manual reporting for our stakeholders and having
the epic name automatically populated in the data would be a life saver! Please
prioritize this!


Cayla Halliday added a comment - 28/Sep/2023 2:47 PM My Team spends hours a
month in manual reporting for our stakeholders and having the epic name
automatically populated in the data would be a life saver! Please prioritize
this!
HP added a comment - 20/Jun/2023 4:50 PM - edited

Using the workaround suggested (Print List) works fine to get the epic name,
however, you lose the Priority values if that is in the result set.

 

With as many people needing this to work properly, can we not just prioritize to
get it fixed? 


HP added a comment - 20/Jun/2023 4:50 PM - edited Using the workaround suggested
(Print List) works fine to get the epic name, however, you lose the Priority
values if that is in the result set.   With as many people needing this to work
properly, can we not just prioritize to get it fixed? 
Kirsten Coppo added a comment - 04/Jan/2023 8:31 PM

Please fix! I have to do a vlook up in excel; what a pain!


Kirsten Coppo added a comment - 04/Jan/2023 8:31 PM Please fix! I have to do a
vlook up in excel; what a pain!
Melanie C added a comment - 04/Jan/2023 7:44 PM

Begging for this to be addressed. 6 years old . . .


Melanie C added a comment - 04/Jan/2023 7:44 PM Begging for this to be
addressed. 6 years old . . .
Debbie Munson added a comment - 14/Dec/2022 5:42 PM

There are multiple tickets on these same topic.  Jira team please consolidate
them so you can see the true magnitude of interest in fixing this.


Debbie Munson added a comment - 14/Dec/2022 5:42 PM There are multiple tickets
on these same topic.  Jira team please consolidate them so you can see the true
magnitude of interest in fixing this.
Peigi MacKillop added a comment - 14/Dec/2022 5:18 PM

This issue is nearly 6 years old, this is beyond poor service and is now parody!


Peigi MacKillop added a comment - 14/Dec/2022 5:18 PM This issue is nearly 6
years old, this is beyond poor service and is now parody!
HP added a comment - 17/Nov/2022 12:12 AM

Here's a simple use case that affects me before every sprint.
I want to be able to look at all the tickets that have been dropped into the
next sprint for planning. I like to sort them by epic name and export them to
Excel using Export to Excel option. I then organize my list in Excel by
different teams, tickets related to Automation, tickets related to Integrations,
Core Dev work, Content work, etc. 

If I can see the epic name in my export, I can quickly move these groups of
tickets in the list to various tabs and then am easily able to see how much work
I am allocating to each group.  Right now, I have to translate the Epic issue id
into Epic names by looking at the Jira list and modifying the excel.

If it was 5-6 tickets, that's doable. I work with at least 60-70 tickets per
sprint. This is very inefficient.

If I had to do this maybe, once in a while, I'd accept it. However, this takes
extra time prior to each sprint planning session. 

I use the same process for looking at my release list, which happens once every
two months, and that list 2-3x as long as the sprint list. 

Just imagine, how much time I could save by exporting the epic name rather than
having to translate it each time. 

 


HP added a comment - 17/Nov/2022 12:12 AM Here's a simple use case that affects
me before every sprint. I want to be able to look at all the tickets that have
been dropped into the next sprint for planning. I like to sort them by epic name
and export them to Excel using Export to Excel option. I then organize my list
in Excel by different teams, tickets related to Automation, tickets related to
Integrations, Core Dev work, Content work, etc.  If I can see the epic name in
my export, I can quickly move these groups of tickets in the list to various
tabs and then am easily able to see how much work I am allocating to each
group.  Right now, I have to translate the Epic issue id into Epic names by
looking at the Jira list and modifying the excel. If it was 5-6 tickets, that's
doable. I work with at least 60-70 tickets per sprint. This is very inefficient.
If I had to do this maybe, once in a while, I'd accept it. However, this takes
extra time prior to each sprint planning session.  I use the same process for
looking at my release list, which happens once every two months, and that list
2-3x as long as the sprint list.  Just imagine, how much time I could save by
exporting the epic name rather than having to translate it each time.   
Rajesh Kancharla added a comment - 18/Aug/2022 4:27 AM

Looking forward for a resolution, Kindly expedite this ticket so that it's
beneficial for wider Jira community of users.


Rajesh Kancharla added a comment - 18/Aug/2022 4:27 AM Looking forward for a
resolution, Kindly expedite this ticket so that it's beneficial for wider Jira
community of users.
Ben Stanford added a comment - 16/Jun/2022 11:21 AM

adding vote.  painful to use the export function without it


Ben Stanford added a comment - 16/Jun/2022 11:21 AM adding vote.  painful to use
the export function without it
Load 10 older comments

PEOPLE

Assignee: Unassigned Reporter: Luiz Farias (Inactive)
Votes: 181 Vote for this issue Watchers: 104 Start watching this issue

DATES

Created: 05/May/2017 1:52 PM Updated: 3 hours ago

 * Atlassian Jira Project Management Software
 * About Jira
 * Report a problem
 * Privacy policy
 * Notice at Collection



Atlassian







This site uses cookies to improve your browsing experience, perform analytics
and research, and conduct advertising. To change your preferences, click Manage
preferences. Otherwise, clicking Accept all cookies indicates you agree to our
use of cookies on your device. Clicking Reject all cookies means you do not
agree to our use of non-strictly necessary cookies on your device.Atlassian
Cookies and Tracking Notice
Manage preferences Reject all cookies Accept all cookies



MANAGE PREFERENCES

When you visit any website, it may store or retrieve information on your
browser, mostly in the form of cookies. This information might be about you,
your preferences or your device and is mostly used to make the site work as you
expect it to. The information does not usually directly identify you, but it can
give you a more personalized web experience. Because we respect your right to
privacy, you can choose not to allow some types of cookies. Click on the
different category headings to find out more and change our default settings.
However, blocking some types of cookies may impact your experience of the site
and the services we are able to offer.
More information
Accept all

STRICTLY NECESSARY COOKIES

Always Active

These cookies are necessary for the website to function and cannot be switched
off in our systems. They are usually only set in response to actions made by you
which amount to a request for services, such as setting your privacy
preferences, logging in or filling in forms. You can set your browser to block
or alert you about these cookies, but some parts of the site will not then work.
These cookies do not store any personally identifiable information.

TARGETING COOKIES

Targeting Cookies

These cookies may be set through our site by our advertising partners. They may
be used by those companies to build a profile of your interests and show you
relevant adverts on other sites. They are based on uniquely identifying your
browser and internet device. If you do not allow these cookies, you will
experience less targeted advertising.

FUNCTIONAL COOKIES

Functional Cookies

These cookies enable the website to provide enhanced functionality and
personalisation. They may be set by us or by third party providers whose
services we have added to our pages. If you do not allow these cookies then some
or all of these services may not function properly.

PERFORMANCE COOKIES

Performance Cookies

These cookies allow us to count visits and traffic sources so we can measure and
improve the performance of our site. They help us to know which pages are the
most and least popular and see how visitors move around the site. If you do not
allow these cookies we will not know when you have visited our site, and will
not be able to monitor its performance.

Back Button


COOKIE LIST



Search Icon
Filter Icon

Clear
checkbox label label
Apply Cancel
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

Reject all Confirm my choices