In my previous organization, there used to be separate sprints for individual projects. The common understanding was that we follow an Agile Release Train and the sprint opening and close date was constant over all ARTs.
In my new organization there is one single sprint for all scrum projects. Now one of my scrum team's release is taking more time so the sprint close will happen in next day. This is an exceptional case because of business priority in terms of value delivery. But other scrum teams can't start next sprint and estimation since the sprint is not closed.
Please educate me on the standard practice and how to handle the scenario. Should we have a single sprint or keep separate sprint for separate teams?
You can probably find this information in SQL with a query like this:
select cfv.issue, cfv.stringvalue, cf.cfname, P.PKey || '-' || issue.IssueNum as IssueKey
from CustomFieldValue cfv
join CustomField CF on CF.Id = CFV.CustomField
join jiraissue issue on issue.id = cfv.issue
join Project P on issue.Project = P.Id
where P.pkey='SCRUM' and cf.cfname='text1';
This works in postgresql, but the syntax might be different for other database types. In my case my project key here is called 'SCRUM' and my custom field name is 'text1' (both without quotes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Olexandr Polinkevych what does this mean "without checking permissions"? You want to get a specific data despite in JIRA you do not have access because of permissions to them?
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.
This is a horrible way to get data from Jira, please consider doing it properly instead.
But, if you must, then you will need to join Project (or hard-code the specific project), customfield (or hard-code it again) and customfieldvalue with Jiraissue to find it. It will also be inaccurate if config has been changed in certain ways, and it will ignore any permissions and security.
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.
It will be quicker for you to work it out for myself. I would never do it this way, so I've got nothing to hand.
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.