Cannot display custom field in Sub-task that uses the same screen schema & layout as a standard task

[Mieke Bond]

The same screen theme is used for the standard issue type and the sub-type type. There is a customer field called “Sprint” in the screen theme. The problem is that I cannot see the same fields that I can see in the standard issue type, in my Sub-type type task.

1. The project is classic with 5 issue types. Sub task is a sub-task type 
2. The Issue Type Scheme contains the same 5 issue types
3. Sub-Tasks are currently ON
4. The Screen Schemes has a Default issue for unmapped, a bug type and a sub-task type. I wasn’t sure if I needed the Sub Task Type. I added it to see if it resolved the problem but it didn’t assist.
5. The project uses 2 screen configurations. The FSCP: Scrum Default Screen Scheme is used for both the standard issue type as well as the sub-task type.
6. The Default Issue Screen Scheme & the layout includes a field for “Sprint”
7. The field “Sprint” is included in the FSCP: Scrum Default Issue Screen
8. The context for the Field “Sprint” is that it is available for issues of any type

What have I missed to display the custom field “Sprint” in the Sub-tasks?

[Andrzej Pasterczyk · Accepted solution]

UPM will use the proxy settings of the host application.

See http://confluence.atlassian.com/display/JIRAKB/Configure+Web+Proxy+Support+for+JIRA

[Sean Spalding]

So, given there's no mention of proxy authentication on that page can I safely assume that this mechanism cannnot do proxy authentication?

[Andrzej Pasterczyk]

See http://confluence.atlassian.com/display/DOC/Configure+Web+Proxy+Support+for+Confluence

Confluence seems to have support for that - guess you can try same approach with Jira :)

[Sean Spalding]

Thanks, the arguments http.proxyUser= and http.proxyPassword= do work (for any JVM based app).

The JIRA doc needs to be updated.