What is the easiest way to extract sprint start and end dates from the JIRA db?
来源： https://stackoverflow.com/questions/8500600/what-is-the-easiest-way-to-extract-sprint-start-and-end-dates-from-the-jira-db
jira-agile
JIRA setup - project constraints so that tasks need to be completed before next set of tasks can begin
问题 How do I add the business logic in a JIRA project where you can proceed to the next stage on only completing the earlier stages. I am aware that JIRA is a Agile scrum team tool, so it inherently is breaking fundamental agile principles. However, I am trying to define a Kanban workflow where a set of tasks needs to be completed before the next set of tasks can begin. I want to implement this business rule in my JIRA board. 回答1: This may not be the ideal solution, but one approach is to use sub
Is there a way to display reviewers information of any given issue in the Jira Scrum Board cards?
问题 Currently, developers have to: click on each card within the "In Review" status in the Jira Scrum Board click on the "Reviews" tab click on the review link finally they are able to see who the reviewers are (if any) I would like to be able to see, at least, the number of reviewers assigned to a task directly from the Scrum Board cards in Jira as this would be much more efficient than going through each card in the "In Review" status (there may be 20 issues at any given time). Developers would
JIRA JQL: Issues resolved in the current sprint
问题 I would like to be able to filter for issues that are have been resolved in the current sprint. Generally this would be used to prevent issues resolved in a previous sprint but delayed in testing (not reopened) showing up when we are discussing what developers achieved this sprint. Closed issues should also appear, but they are not a problem, as if they were closed last sprint, they wouldn't roll over into this one anyway. In mock-JQL, it would go something like this: project = "Project name"
How to get JIRA Agile issues assigned to the current sprint for the current user using the JIRA REST API?
问题 I'm getting started working with the JIRA REST API. I've learned how to get all the issues assigned to the current user: rest/api/2/search?jql=assignee=currentuser() ...now I am trying to filter those by the current sprint. I think this functionality is provided by the JIRA Agile (Greenhopper) plugin, but I can't find any documentation for it. I came across some interesting data which appears to be the identifier for the sprint that the issue is assigned to: customfield_10005: [ "com
How to get JIRA Agile issues assigned to the current sprint for the current user using the JIRA REST API?
I'm getting started working with the JIRA REST API. I've learned how to get all the issues assigned to the current user: rest/api/2/search?jql=assignee=currentuser() ...now I am trying to filter those by the current sprint. I think this functionality is provided by the JIRA Agile (Greenhopper) plugin, but I can't find any documentation for it. I came across some interesting data which appears to be the identifier for the sprint that the issue is assigned to: customfield_10005: [ "com.atlassian.greenhopper.service.sprint.Sprint@3094f872[rapidViewId=30,state=CLOSED,name=Sprint 2014-06-02
JIRA: Epics vs Labels vs Components
问题 This blog has a definition of epics in JIRA: Epics are significantly larger bodies of work. Epics are feature-level work that encompasses many user stories. Using the above example, an epic might be the entire account management feature and the ability to see previous purchases. So if (as a product owner) I have a large feature I want delivered that will comprise many smaller tasks and likely span sprints, then an epic is a good choice. However, I could just as easily create a (using the
JIRA: Epics vs Labels vs Components
This blog has a definition of epics in JIRA: Epics are significantly larger bodies of work. Epics are feature-level work that encompasses many user stories. Using the above example, an epic might be the entire account management feature and the ability to see previous purchases. So if (as a product owner) I have a large feature I want delivered that will comprise many smaller tasks and likely span sprints, then an epic is a good choice. However, I could just as easily create a (using the example from the blog) "Account Management" component, and any task related to that feature have that