About en » 履歴 » バージョン 40
Akiko Takano, 2014/02/20 02:20
1 | 10 | Akiko Takano | {{>toc}} |
---|---|---|---|
2 | |||
3 | 1 | Akiko Takano | h1. Issue Template plugin |
4 | |||
5 | 2 | Akiko Takano | This is a plugin to generate and use issue templates, and its objective is to *support user's issue creation work*. |
6 | 1 | Akiko Takano | |
7 | 40 | Akiko Takano | h2. Information page on Redmine.org |
8 | |||
9 | * http://www.redmine.org/plugins/issue_templates |
||
10 | |||
11 | 2 | Akiko Takano | h2. Download |
12 | |||
13 | 21 | Akiko Takano | * "bitbucket":https://bitbucket.org/akiko_pusu/redmine_issue_templates/ |
14 | 38 | Akiko Takano | ** "https://bitbucket.org/akiko_pusu/redmine_issue_templates/downloads (You can download zip/tgz) |
15 | 2 | Akiko Takano | |
16 | 1 | Akiko Takano | h2. Features |
17 | 2 | Akiko Takano | |
18 | * It works as project module. |
||
19 | * Member who has "Manage Template" right can create issue templates *based on trackers*. |
||
20 | ** Also add help message for templates, because the way to use templates may be different between projects. |
||
21 | * Member who has "Use Template" right can see the template and use them when creating new issue. |
||
22 | 39 | Akiko Takano | * Child project can use inherited templates from parent project. (Since ver 0.0.6) |
23 | 1 | Akiko Takano | |
24 | h2. Plugin installation |
||
25 | 3 | Akiko Takano | |
26 | # Copy the plugin into the vendor/plugins directory |
||
27 | # Migrate plugin: rake db:migrate_plugins RAILS_ENV=production |
||
28 | # Start Redmine |
||
29 | # Enable the module on the project setting page. |
||
30 | 1 | Akiko Takano | |
31 | 28 | Akiko Takano | h2. Uninstall plugin |
32 | |||
33 | 29 | Akiko Takano | h3. Run rake task |
34 | 28 | Akiko Takano | |
35 | ** rake redmine:plugins:migrate NAME=redmine_issue_templates VERSION=0 |
||
36 | |||
37 | Above rake task will remove the related records to redmine_issue_templates from schema_migration table. |
||
38 | In additon to this, issue_templates and issue_template_settings tables will be also removed. |
||
39 | |||
40 | 29 | Akiko Takano | h3. Manual uninstall |
41 | 28 | Akiko Takano | |
42 | In some situation, rake task to uninstall may be failed. To uninstall plugin manually, please remove these records and tables from your database. |
||
43 | |||
44 | * Remove records from schema_migration table related to issue_templates. |
||
45 | ** DELETE FROM schema_migration WHERE version LIKE '%redmine_issue_templates'; |
||
46 | |||
47 | * Drop issue_templates and issue_template settiongs. |
||
48 | 30 | Akiko Takano | ** DROP TABLE issue_templates; DROP TABLE issue_template_settings; |
49 | 28 | Akiko Takano | |
50 | 31 | Akiko Takano | h2. Permission Settings (as Redmine Admin) |
51 | 1 | Akiko Takano | |
52 | 4 | Akiko Takano | Now this plugin works as project module, and three permissions are defined. |
53 | |||
54 | # Show template |
||
55 | # Edit template |
||
56 | ** Right to create/edit templates. |
||
57 | # Manage template |
||
58 | ** Right to add help message for templates, such as usage of templates. |
||
59 | |||
60 | (!) Note: These templates are available only for its project. |
||
61 | 7 | Akiko Takano | (!) Note: Only Redmine administrator can set ermissions for issue templates. |
62 | |||
63 | |||
64 | 1 | Akiko Takano | > !permission.png! |
65 | 31 | Akiko Takano | |
66 | h2. Enabled Issue Templates as Project Module |
||
67 | |||
68 | Now this plugin works as project module. |
||
69 | So, project manager needs to check this plugin at project module settings page for activation. |
||
70 | 1 | Akiko Takano | |
71 | 32 | Akiko Takano | !set-as-project-module.png! |
72 | 4 | Akiko Takano | |
73 | 11 | Akiko Takano | h2. Usage & Screen shots |
74 | 5 | Akiko Takano | |
75 | h3. Use templates |
||
76 | |||
77 | 6 | Akiko Takano | User who has "show templates" permission can use templates when creating issue. |
78 | 16 | Akiko Takano | First, enable, selectable templates related with the tracker are shown as pulldown menu. |
79 | 6 | Akiko Takano | |
80 | 16 | Akiko Takano | Select template from pulldown, ajax request is posted and template body is loaded into issue description field. |
81 | |||
82 | 6 | Akiko Takano | |
83 | 16 | Akiko Takano | > !use_template1.png! |
84 | |||
85 | 35 | Akiko Takano | NOTE: Since templates are associated with a tracker, that template pulldown menu i changed if the tracker is changed at then new issue page. And if selected tracker has no associated templates, issue template pulldown is blank. ( only "---" text is shown.) |
86 | |||
87 | 37 | Akiko Takano | > !template-pulldown-is-blank.png! |
88 | 35 | Akiko Takano | |
89 | 5 | Akiko Takano | h3. Create/Edit templates |
90 | 12 | Akiko Takano | |
91 | 1 | Akiko Takano | To access create / edit templates menu, click "Issues" or "New Issue" project tab, and you can see the menu at the sidebar. |
92 | |||
93 | 13 | Akiko Takano | Click "Add template" and the form for creating template will be shown. |
94 | |||
95 | 17 | Akiko Takano | And each template is related to some tracker, so that if you change tracker of new issue, template pulldown is also reloaded and updated related to the tracker. |
96 | |||
97 | 16 | Akiko Takano | > !gotomenu.png! |
98 | 13 | Akiko Takano | |
99 | 16 | Akiko Takano | > !add-template.png! |
100 | 12 | Akiko Takano | |
101 | (!) Note: This is not shown without "show templates" permission. |
||
102 | 5 | Akiko Takano | |
103 | 14 | Akiko Takano | h3. Manage project templates |
104 | 1 | Akiko Takano | |
105 | 14 | Akiko Takano | Now this is optional setting. |
106 | Who has manage template permission can set custom help message for template usage on his/her project. |
||
107 | 1 | Akiko Takano | |
108 | 14 | Akiko Takano | This help message will be shown on the "New Issue" page, beside template pulldown. |
109 | |||
110 | 16 | Akiko Takano | > !manage-template.png! |
111 | 15 | Akiko Takano | |
112 | Here is a screenshot of custome template help message. |
||
113 | |||
114 | 16 | Akiko Takano | > !template-help.png! |
115 | 18 | Akiko Takano | |
116 | 25 | Akiko Takano | h3. Change Template order |
117 | 18 | Akiko Takano | |
118 | 25 | Akiko Takano | In case a tracker has some related templates, you can reorder template on index page. |
119 | 19 | Akiko Takano | |
120 | 25 | Akiko Takano | h3. Default template setting |
121 | |||
122 | If a template marked as default, template text will be loaded when tracker is changed on creating issue page. |
||
123 | |||
124 | 26 | Akiko Takano | For example, *Bug* tracker has 3 templates and "Bug3 default" template is marked as default. |
125 | |||
126 | 25 | Akiko Takano | !template-list.png! |
127 | 26 | Akiko Takano | |
128 | At the new issue page, when user selects Bug tracker, soon default template text is appended to description field. |
||
129 | |||
130 | 25 | Akiko Takano | !load-default-template.png! |
131 | |||
132 | 19 | Akiko Takano | h2. Future plannning / Feedback |
133 | 20 | Akiko Takano | |
134 | 18 | Akiko Takano | h3. Plannning |
135 | |||
136 | * Use global templates. |
||
137 | 27 | Akiko Takano | |
138 | 18 | Akiko Takano | |
139 | h3. Feedback |
||
140 | |||
141 | 1 | Akiko Takano | * Feedback would be appreciated. You can send from issue tracker on bitbucket or tracker on this project. |
142 | 25 | Akiko Takano | * Translations, ui idea, css are also appreciated. |