| Key: |
JRA-7882
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Duplicate
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Rémy Mouton
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Duplicate
|
|
This issue duplicates:
|
|
JRA-6549
Allow to make fields required on per screen/workflow step basis
|
|
|
|
|
|
|
|
It would be nice to have an attachment field in a transition view, and even be able to make it required or to write a validator that checks if an attachment has really been added.
(This is slightly different from, but comparable with, a custom field of type attachment.)
|
|
Description
|
It would be nice to have an attachment field in a transition view, and even be able to make it required or to write a validator that checks if an attachment has really been added.
(This is slightly different from, but comparable with, a custom field of type attachment.) |
Show » |
|
It is already possibel to display attachment field on workflow transition screens (
JRA-1904). All you need to do is create a new screen and associate a transition with it:http://www.atlassian.com/software/jira/docs/latest/fieldscreens.html
At the moment it is not possible to make that field required on one screen. This is tracked by:
JRA-6549It is is possible to write validator and use it on a transition.
Do you mind if we resolve this issue as duplicate, and track work on this using
JRA-6549? You can add any suggestions you have toJRA-6549.Thanks,
Anton