Hi,

This is a bulk update to specific issues in the JIRA (JRA) project

As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

Best regards
Josh Devenny and Roy Krishna
JIRA Product Management

Old issue but maybe I can get some response: I'm on 3.13.2. I just cloned an issue that had several closed subtasks, and they were reset to open. Fine. BUT....the one subtask that was in progress was given an Open status, but the tranisitions were Resolve and Close (indicating it was still in progress). So the tranistions aren't matching with the status.

Seen anything like this?

No, you should give an option wheter to subtask should behold its workflow status or not.

Hi Cécile,
Not a bug, this was by design.

Though I do see the use case for it so I think we should give the user an option whether to reopen subtasks or leave tehm closed.

Cheers,
Nick