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.
Related
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.
We are using TFS 2015 together with the CMMI process template and I have just found out that Issues do appear on the backlog if they are a child of a Feature or a Requirement work item type. If the Issue is standalone (has not link to one of the two mentioned work item types) it is not visible on the backlog.
I guess that someone has made some hacks here in order to make this possible. Originally, only Epics, Features, Requirements, Tasks, and Bugs should appear on the backlog.
I have checked the Issue work item type definition as well as the processconfiguration.xml and the categories.xml which look quite ok from my point of view.
Are there any another places where one could define which work item types should be visible on the backlog?
Thanks a lot for giving support.
To add a WIT on backlog, the three files below need to updated:
WIT Definition
Categories Definition
ProcessConfiguration Definition
You can check the required changes on this link: Add work item types to backlogs and boards to see if these changes had been applied on your project. If yes, revert these changes, then the Issue should disappear from the backlog.
You should not use the "child" link to associate with Issues.
The Parent/Child link is used for the backlog and I would think that the Issues are appearing because of this.
Try changing the Parent/Child link to Related.
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.
I have a project for which I can add and edit issues. When I create a board, I normally map issue types to board columns (e.g. if I have 5 todo issues not in the current board, normally the system lets me map todo(5) to the todo column).
For my current project, all my issue statuses are marked as having (0) issues associated, yet I have a dozen issues which should appear. Please see the attached screenshot.
Cheers,
Albert.
It seems the board was somehow corrupted. I just discarded it and created a new board, and now the issues appear as expected.
The boards: Work/Backlog/product backlog/board(the stories/backlogitems) and on Work/board(tasks) can we have different column mappings per teams? Currently the type - value pairs are stored in CommonConfiguration, so it is project based, can we change it to be Team relative?
This totally depends on which update you are on (if you are using on-premise TFS). If your TFS deployment is Update 2 or higher - or you are using TFService - you can customize the "Kanban Board" (the board that shows work items on the backlog), link here: http://blogs.msdn.com/b/bharry/archive/2013/02/01/customizable-kanban-swim-lanes.aspx. This allows you to change the columns, per team, without changing the workflow of work items themselves.
As for the Task board, you can customize it, but only for an entire team project. This must also be done via the CommonConfiguration file.