Jira Cloud was unable to find the target story when the host story was in an active sprint. Is there any reason for this or is this a defect?
It sounds like a bug, but I think there's something wrong somewhere else -
A developer would have had to have specifically sat down and written code to make it behave like that, and I can't think that any developer would have. Bugs are usually there because something is wrong or has been missed, you'd actually have to write code to make stuff behave like this.
The other thing it could be is permissions - if you didn't have the permission to edit the target story, then you would not be offered it as a potential parent issue. Does your workflow restrict editing while things are in parts of their lifecycle?
No our workflow is out of the box. No logic as of yet. It could be permissions. We are working on upgrading the SMs privileges as we speak.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.