We have two scrum teams working on a common product, so we have some cross-platform tasks that could apply to either team.
How would I create a label that would allow the task to appear in all backlogs/boards?
The issues that appear on a board are defined by a JQL filter. Typically this will simply select all the issues for a given project like this:
project = "myproject"
But there is nothing stopping you from modifying it. As an example a board filter could use:
project = "myproject" or labels in ("mylabel")
That would show all the issues for the project 'myproject' and any issues that include a label 'mylabel'.
The board filter can be modified in the 'Configure' menu on the board under 'General'.
I am using currently the field label, and each team agile board will use it to filter their own user stories and by putting both team names (team_1, team_2) on the user story label, both teams will see the same user story.
Related
I have created a jira board in which I want to show epics of multiple project that contain a value within the custom field Objective. For this I created the following filter:
type = Epic AND "Objective[Labels]" is not EMPTY ORDER BY created DESC
When I check the filter it is showing all the epics (from multiple projects) which have a value for Objective. When I use the filter within a board it is only showing the epics of one project.
Update:
There was a warning in the board configuration that certain states where not mapped. After dragging the unmapped states to the proper column the issues appeared. The states that I needed to map (todo, in-progress, etc) where the default ones for a project.
Must i map for every new project in which a epic with label objectives is created the states to the proper columns?
There was a warning in the board configuration that certain states were not mapped. After dragging the unmapped states to the proper column the issues appeared. The states that I needed to map (todo, in-progress, etc) were the default ones for a project.
I have my one project which is getting expanded in different countries. I want to create one single project and sub project for different country in JIRA to track separately the progress
You can have multiple boards in Jira that all point to the same project. All you need is some way of differentiating between them.
For example you could have a custom field that indicated the target country for an issue.
The steps you would take are as follows:
Create the project
Add the custom field to the issues in that project
Create several filters, with each one selecting all the issues for a given country in your custom field
Create a board for each filter
Based on your requirements: if you do not want each sub-project visibility to other sub-project members, you should create a new project for every subproject and use either filters and/or dashboards to monitor them.
If visibility is not a problem, You might consider using components for each sub-project.
From one day to another, changing the issue filter slightly, my Kanban board's board configuration in JIRA went empty. I use the following JQL as a filter within the board configuration:
project = "My amazing project" and fixVersion in unreleasedVersions()
ORDER BY priority DESC
The above filter does not work. What is working, though, is
project = "My amazing project" and fixVersion = "v1337"
ORDER BY priority DESC
Interestingly, the first query works in JIRA's issue explorer and gives me back the 11 results I expect. As you see in the screenshot below, I have no quick filters enabled. Neither do I have any sub-filter added, nor am I hiding any older issues. Where did all the cards go?
I am using Atlassian Jira Project Management Software (v8.2.3#802003-sha1:5986657), and I am not an administrator of that installation, only of the project.
Further reading
community.atlassian.com: Kanban board is empty
There is a dedicated problem page provided by Atlassian:
Symptoms
The issues are not visible in Kanban board, but when you are in board configurations >> columns you can see number of issues.
Cause
As Kanban board deals with version of the issues, the field named Fix Version/s should not be hidden
This is because the default Kanban board sub-filter(Board Configure >> General) has been set to
fixVersion in unreleasedVersions() OR fixVersion is EMPTY
The page also describes a rather complicated workaround. My workaround was much simpler:
Change the JQL query to project = "My amazing project" only.
Create a subfilter fixVersion in unreleasedVersions() ORDER BY priority DESC.
I do not understand why it has to be this way, but it does the job.
We have just started using Team Foundation Server (version 15). I thought I could use Epics to organize features and other work elements but when I create an Epic I don't see where it is and can't see how to associate a Feature to it. Am I misunderstanding the use of Epics? I have been given a single project called Workflow under which I need to manage multiple clients. Epics seems a good container for a client level object.
Thank you!
From your team's backlog page, click the gear icon (gear icon) to open the common configuration team settings.
Click the Backlogs tab and check the boxes of those backlog levels you want your team to manage.
Source : Microsoft's documentation
We have a department team section in JIRA setup as a project and I have been asked to create Kanban boards and set the section up ready to use but I'm not sure the best way to apply the work the department team is managing into JIRA.
We want to have Kanban boards for two different specialties and for e.g. one of the specialties we have two projects and one of the projects has a subproject and also one of the projects may sometimes overlap with both specialties.
For example:
Build team
Development Kanban Board
Project A
Project Sub Project/Stream A
Project Sub Project/Stream B
Project B
Test Kanban Board
Project A
My current thoughts are:
Project = Team
Component = Project A
Epic = Project Sub
Project/Stream
Labels = Specialty Kanban Board
Is the above correct or is there another approach that would be best practice for this scenario? At the moment I think we are tied into having the Project in JIRA set as the team
Usual practice is to make your projects correspond to JIRA projects (thus the name). You can set up the filters for Kanban boards to bring in issues from multiple projects according to whatever criteria you want. This will make it easier if issues need to flow from the dev team to the test team. The "Team" can be defined by assignee, status, or another field if you prefer. Epics are good for time-bounded subprojects, components are good for ongoing subelements (e.g. UI, database, etc.).