I am using Jira Cloud for our projects (say A, B and C). I have labels for project A, say, AL1, AL2 and AL3.
When I am trying to add labels for issues in Project B, Labels from Project A (AL1 etc) show up as options, even though they may not be relevant. Due to the # of labels in each project, this is becoming cumbersome to use.
What settings do we need to configure in Jira to restrict issue labels to the Project Context?
We cannot restrict a Label inside a particular project, it will be global. Instead
Can create a custom field for handling the labels.
Or
Can use Components field. But we cannot create a component on the fly, it will be created in the settings.
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.
Is there any way with or without a plugin to have two or more separate Xcode workspaces open at the same time ?
I want each with a different theme / colour scheme.
I often have two projects open which may have the same name, and would like to allow myself to easily identify which project I am using.
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.
Our code is branched in TFS along project lines, and each has its own separate build process
We label each project with the build number, e.g. Build_1, etc however I made the dumb mistake of forgetting that TFS labels must be unique and forgot to label my project with the name of the project.
To explain, I have labelled the P5624 folder four times with Build_1, Build_2, Build_3 & Build_4 when I should have used labels like P5624-Build_1, etc.
So, I am looking for a way to rename the labels. I couldn't find anything directly related on SO, and the microsoft Help on the TF Label command (link here) doesn't give any indication that it can be done.
We don't do any automated builds or have anything that relies on a label name, so even if your solution is a "do it at your own risk" then I would still be happy to hear it.
Renaming Labels is not supported by TFS. You can only create a new Label based on the old Label you want to remove.
If your are using Visual Studio, here are the steps how to do it
Right click the folder at Source Control Explorer to open
ContextMenu and select 'Apply Label'
Change the Version-Combobox at the bottom to Label and find the old Label "P5624"
Name the new label "P5624-Build_1" and create it
Delete the old label if it isn't needed more.
We have a fairly standard release procedure using Visual Source Safe for labeling a build before it is released. This allows us to do a get from that label if there are any problems and use it to branch if changes are necessary.
We have several different projects and always label using the builds version number.
e.g. "V1.0"
After moving some projects to TFS we have noticed that if you try to label using the same version number as another solution e.g. Solution A and Solution B both release "V1.5" then TFS will not let you do this as the Label name is treated globally. After reading a few blogs on the subject which discusses how TFS labels are not a point in time but a collection of files I am thinking that we will have to start including the project name in the label to get around this e.g. label as "Project A V1.5" and "Project B V1.5". Does this sound like the right approach?
If you haven't read Brian Harry's Why TFS labels aren't like SourceSafe labels, please do.
Basically the answer to your question is YES!