Project

General

Profile

Actions

Feature #16207

closed

Use query name as the file name when exporting queries

Added by Martin Seener about 10 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Issues
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

By now if you export a custom issue query for ex. as a PDF, its named "issues.pdf" which says nothing and is inconvenient to handle. It would be much better to use the custom query name as the filename (whereas spaces are written as underscores). See my attached image as an example we use it would be cool to directly save it as "incidents_of_last_month.pdf".

Just better: Optionally add a date to it "incidents_of_last_month_2014-02-03.pdf".

We use such exports for some partners so this would really make our lifes easier


Files

incidents.png (27.6 KB) incidents.png Martin Seener, 2014-03-03 14:01
file_naming.diff (3.66 KB) file_naming.diff Mathias Nestler, 2014-04-05 21:00
file_naming2.diff (4.56 KB) file_naming2.diff Mathias Nestler, 2014-05-12 23:18
feature-16207.patch (6.5 KB) feature-16207.patch Mizuki ISHIKAWA, 2019-08-23 08:36
feature-16207-r19982.patch (6.41 KB) feature-16207-r19982.patch Go MAEDA, 2020-08-22 08:16
feature-16207-r21769.patch (6.34 KB) feature-16207-r21769.patch Go MAEDA, 2022-08-12 07:24

Related issues

Related to Redmine - Defect #38182: Exporting users query does not use the query name as file nameClosed

Actions
Actions #1

Updated by Mathias Nestler about 10 years ago

change including tests attached

Actions #2

Updated by Martin Seener about 10 years ago

  • Status changed from New to Resolved

see attached file_naming.diff for the resolving code parts. please merge and close this.

Actions #3

Updated by Toshi MARUYAMA about 10 years ago

  • Status changed from Resolved to New

You need handle non ASCII filename.
See #16207.

Actions #4

Updated by Toshi MARUYAMA about 10 years ago

Toshi MARUYAMA wrote:

You need handle non ASCII filename.
See #16207.

Sorry, it is #16711.

Actions #5

Updated by Mathias Nestler about 10 years ago

Added fix to handle non ASCII filenames. The new diff file contains the complete change.

Actions #6

Updated by Mathias Nestler almost 10 years ago

Toshi MARUYAMA wrote:

Toshi MARUYAMA wrote:

You need handle non ASCII filename.
See #16207.

Sorry, it is #16711.

Have you seen the fix?

Actions #7

Updated by Mathias Nestler almost 10 years ago

Mathias Nestler wrote:

Toshi MARUYAMA wrote:

Toshi MARUYAMA wrote:

You need handle non ASCII filename.
See #16207.

Sorry, it is #16711.

Have you seen the fix?

Actions #8

Updated by Mizuki ISHIKAWA almost 5 years ago

I modified patch file_naming2.diff to apply to the trunk.
This patch renames issues.csv, issues.pdf and timelog.csv to custom field name.

Actions #9

Updated by Go MAEDA over 4 years ago

  • Target version set to Candidate for next major release
Actions #10

Updated by Go MAEDA almost 4 years ago

Update the patch for r19982.

Actions #11

Updated by Go MAEDA almost 2 years ago

Setting the target version to 5.1.0.

Actions #12

Updated by Go MAEDA almost 2 years ago

  • Category changed from PDF export to Issues
Actions #13

Updated by Go MAEDA almost 2 years ago

  • Subject changed from File naming of exported custom queries to Use query name as the file name when exporting queries
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the patch. Thank you.

Actions #14

Updated by Go MAEDA almost 2 years ago

  • Status changed from New to Closed
Actions #15

Updated by Go MAEDA over 1 year ago

  • Related to Defect #38182: Exporting users query does not use the query name as file name added
Actions

Also available in: Atom PDF