Project

General

Profile

Actions

Feature #16207

closed

Use query name as the file name when exporting queries

Feature #16207: Use query name as the file name when exporting queries

Added by Martin Seener over 12 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Issues
Target version:
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 1 (0 open — 1 closed)

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

Updated by Mathias Nestler over 12 years ago Actions #1

change including tests attached

Updated by Martin Seener over 12 years ago Actions #2

  • Status changed from New to Resolved

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

Updated by Toshi MARUYAMA over 12 years ago Actions #3

  • Status changed from Resolved to New

You need handle non ASCII filename.
See #16207.

Updated by Toshi MARUYAMA over 12 years ago Actions #4

Toshi MARUYAMA wrote:

You need handle non ASCII filename.
See #16207.

Sorry, it is #16711.

Updated by Mathias Nestler over 12 years ago Actions #5

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

Updated by Mathias Nestler over 12 years ago Actions #6

Toshi MARUYAMA wrote:

Toshi MARUYAMA wrote:

You need handle non ASCII filename.
See #16207.

Sorry, it is #16711.

Have you seen the fix?

Updated by Mathias Nestler about 12 years ago Actions #7

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?

Updated by Mizuki ISHIKAWA about 7 years ago Actions #8

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.

Updated by Go MAEDA about 7 years ago Actions #9

  • Target version set to Candidate for next major release

Updated by Go MAEDA about 6 years ago Actions #10

Updated by Go MAEDA over 4 years ago Actions #11

Setting the target version to 5.1.0.

Updated by Go MAEDA over 4 years ago Actions #12

  • Category changed from PDF export to Issues

Updated by Go MAEDA about 4 years ago Actions #13

  • 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.

Updated by Go MAEDA about 4 years ago Actions #14

  • Status changed from New to Closed

Updated by Go MAEDA almost 4 years ago Actions #15

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

Also available in: PDF Atom