Assign Team to Sub-Task on Advanced Roadmap Plan

[Matt Steadman]

Reading through the documentation on Advanced Roadmaps, it looks like the intended use is to only be able to assign a Team to the Story. Is there any way anyone has found to be able to have a Team assigned to a Sub-Task of a Story? We have a use case where the Story Issue is a main idea and the Sub-Tasks of that Story would be intended for different Teams to accomplish a piece of work on that. Thanks for any response ahead of time.

[James Youngman · Accepted solution]

I can't believe it. A stupid user error. ARGGGGGGGGGGGGGGGGG!

Thank you Tim.

[Timothy · Accepted solution]

It's /rest/api/2/issue/{issueIdOrKey}/attachments not attachment (unless its a different in another API http://docs.atlassian.com/jira/REST/5.2.11/#id167094).

[James Youngman]

This is closed.

[Nic Brough -Adaptavist-]

You close these by marking one or more answers as correct. I'd recommend your "user error" one :-)

[James Youngman]

* HTTP error before end of send, stop sending

<

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><status><status-code>404</status-code><message>null for uri: http://10.24

9.88.155/jira/rest/api/2/issue/SR-2320/attachment</message></status>* Closing connection 0

[James Youngman]

Here is the code:

curl.exe -D- -v -u xxxx:xxxx -X POST -H "X-Atlassian-Token: nocheck" -F "file=@c:\\logs\\AIFDBScripts.zip" http://mysite/jira/rest/api/2/issue/SR-2414/attachment

The error is: HTTP error before end of send, stop sending

[Timothy]

Are you sure that this is the only response? What is the respond code?

[Timothy]

What error?

[Nic Brough -Adaptavist-]

Which example code?

Although, that error usually means your network has failed for some reason - pulling a network cable, proxy server not letting you in, packet loss etc.

[Nic Brough -Adaptavist-]

Which example code?

Although, that error usually means your network has failed for some reason - pulling a network cable, proxy server not letting you in, packet loss etc.