Derek Fields _RightStar_ Community Champion

This seems to me to be a simple Two-Dimensional Dashboard gadget. You would create a filter that lists all of the issues that you want to include. Then set the Y-Axis to be the Sprint and the X-Axis to be the Status

I'm not sure I understand your use case. You can set a Condition on a transition in the User Story workflow that won't allow the transition until all sub-tasks have reached a particular status (e.g., Done). If you aren't using Subtasks on the User Stories, then you need a plugin to provide that same functionality on linked…

You are thinking too narrowly. This field is used to associate the Issue with the Release. Don't think about it as Bug Fixes but as the collection of issues that are associated with this release. You should Affects Version/s to identify which Releases are affected by the bug. Since new functionality doesn't affect existing…

The Releases issue list is based on Fix Version/s - creating a custom field won't make the issue show up on that list. Why do you need a different release custom field from Fix Version/s? 

Thanks for the quick reply. That is what I thought but I wanted to see if someone could confirm for me.

You don't need to break the stories into sub-tasks unless you want to do that. Story Ponts are entered through your Sprint board, generally during Sprint Planning or Backlog Grooming. When you are ready, you put an Original Estimate into the Story and then use Worklogs to deduct from the Original Estimate. You need to turn…

I would be very interested to know what the problem was. I am getting the same error and can't find the cause.

Using issue.store() instead of IssueManager.updateIsssue worked - which is frustrating. It is also risky as a long-term solution, since store() is deprecated. The good news is that I should only have to use it for a short term fix. I also determined that it is possible to do a direct database update into the…

What is the point of setUpdated () if it doesn't do anything?

The platform that each add-on supports is marked under the name of the add-on in the Marketplace. As you can see, the plugin above indicates that it is only for Jira Server. This plugin specifically indicates Jira Coud and Jira Server but it is not officially supported by the vendor.

Assuming that you are using G Suite account, you are covered by using the Google 2FA mechanism. It would be redundant to also turn it on in Jira as well. Of course, you have to trust Google's authentication to be safe (I do, but there are those who don't)

Active Directory Attributes Sync has a Copy Property post-function that will allow you to copy a parameter from AD into a Jira field. You would use this to populate the Approvers field with the Manager. The Manager field from AD needs to be the Jira username for this to work. 

There may be a plugin that can help you with this, but I haven't seen it. You can't think of Jira like a relational database, even though it uses one for storage. JQL only returns one type of object - an Issue. You can't "join" across issue types to enrich one issue with data from another without actually replicating the…

Your question is not very clear, but I think you are asking about JIRA Service Desk approvals, which don't require a custom field. You simply need to indicate in the JSD workflow that an approval is needed. The Manager who is assigned to approve will be able to access the same information on the portal that user can see…

Jira and Confluence are different products. You can install both Jira and Confluence on the same server or VM but they run in different tomcat environments and listen on different ports. 

Your JQL works fine for me. Are you using Portfolio (which is how you would have Initiatives and Parent Link)? If so, have you associated the Epics with the Initiatives and committed your changes in the Plan?

Great - you answered my question. It is not clear from the documentation (or I just did read it closely enough) that the behaviour of the field is triggered on the change to the field. Now that I see it, it becomes pretty obvious.