Feature #16207
File naming of exported custom queries
Status: | New | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | PDF export | |||
Target version: | Candidate for next major release | |||
Resolution: |
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
History
#1
Updated by Mathias Nestler almost 7 years ago
- File file_naming.diff
added
change including tests attached
#2
Updated by Martin Seener almost 7 years ago
- Status changed from New to Resolved
see attached file_naming.diff for the resolving code parts. please merge and close this.
#3
Updated by Toshi MARUYAMA almost 7 years ago
- Status changed from Resolved to New
You need handle non ASCII filename.
See #16207.
#4
Updated by Toshi MARUYAMA almost 7 years ago
#5
Updated by Mathias Nestler almost 7 years ago
- File file_naming2.diff
added
Added fix to handle non ASCII filenames. The new diff file contains the complete change.
#6
Updated by Mathias Nestler over 6 years ago
#7
Updated by Mathias Nestler over 6 years ago
#8
Updated by Mizuki ISHIKAWA over 1 year ago
- File feature-16207.patch
added
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.
#9
Updated by Go MAEDA over 1 year ago
- Target version set to Candidate for next major release
#10
Updated by Go MAEDA 7 months ago
- File feature-16207-r19982.patch
added
Update the patch for r19982.