How can I display all pendings tasks in Plastic SCM when create a new
child branch?
Goto Preferences -> Issue trackers -> Issue query limit and set your display limit. (e.g. 100)
Related
I was wondering if it was possible to force the update of several report when I update one of them (update master -> update slave1, slave2 and slave3) and if it was a good practise.
Thanks in advance for your help.
Explication Schema
I found a way to approximately do it, I will give you a sample case :
In this sample, we want to have a "master report" and a "slave report" which will copy the content of the master.
1) Build the master report (just a classic text field inside) and publish it on jasperserver
2) Build the slave report, put only a subreport in it with this expression "repo:/path_to_your_master_folder/master_report_files/main_jrxml" then publish it
3) Check with the main_jrxml file of your slave report that you have a subreport with the good expression in it (can be buggy sometimes)
-> Now when you update the master report and publish it again (change the static text for example), the slave report is updated
WARNING : This method doesn't work if you have external config (images, input controls, ...) so be prepared to copy them with another method
Hope this will be helpfull !
Currently, we manually set the iteration as Current iteration in Azure Devops (VSTS):
Could you please help how this can be automated? So we do not have set for every iteration.
I have tried all possible ways through web UI.
To set a default Iteration path for newly created workitems, go to 'Project Settings > Team Configuration'.
Use #CurrentIteration for the default iteration path. This will automatically map to todays valid iteration (by start and end date).
There is no need to do that manually.
Once you work with iteration dates (Start date, End date) for your sprints, Azure DevOps will automatically determine which sprint is the current one.
All steps to schedule a sprint date are described here.
Tasks are a child of Backlog Items or Bugs and by default inherit the iteration of the Backlog Item or Bug that they are created under.
So you don't have to always set them manually, do the following:
If it is a new backlog item,
Go to the Backlog for your current sprint, create a backlog item or bug and the iteration path will automatically be set to the current sprint because you created it in the context of the sprint. Now when you add tasks they too will have the same iteration.
If backlog item exists but no tasks yet,
If you already have a backlog item that is sitting on the backlog (not in a sprint backlog yet) move the backlog item to your sprint first, then create tasks underneath
If your backlog items and tasks are already created,
You can set the iteration path for all of them at once by using multi select and edit (shift+click) to select then select ... menu and select edit. You can then select Iteration Path for the field and select the sprint you want to set and then click Save.
So after setting up my teams, I need to define separate sprints for each. I notice that when I go under project settings > work > iterations, I see the default set defined for a new project. The name that these default iterations fall under is the same name as the project. So that leads me to ask
- Is the name Im looking at for a new project that has these default iterations, the name of the project or the default team?
In other words, Im looking at setting up my team/iteration structure like this, is there a better or best-practice approach (when using multiple teams within a single team project) ?
Below, I defined new children of the root node (again, is that the project name or default team with the same name?)
root-name-here
|__Team1
|__Sprint1
|__Sprint2
|__Sprint3
|__Sprint4
|__Sprint5
|__Sprint6
|__Team2
|__Sprint1
|__Sprint2
|__Sprint3
|__Sprint4
|__Sprint5
|__Sprint6
|__Sprint1
|__Sprint2
|__Sprint3
|__Sprint4
|__Sprint5
|__Sprint6
The "default" set of iterations that are now at the same level, can I simply remove them?
You can config different iterations based on different teams. Detail as below:
PS: I share the steps with New Navigation, if you want to turn on the New Navigation, set as below:
Click profile -> Preview features -> then turn on the New Navigation).
1. Add iterations with the structure you need
In Project settings -> Project configurations -> Iterations Tab -> Add iterations as below (as you listed):
2. Specify different iterations for different teams
In Project settings -> Team configurations -> select different iterations for different teams. Besides, you can also set default iteration and backlog iteration for different teams.
Such as:
Select Git2\Sprint 1~6 to Git2 Team:
Select Git2\team 1\Sprint 1~6 to teamA:
Select Git2\team 2\Sprint 1~6 to second team:
Now when open backlogs for different teams, only the specified iterations are listed.
You can define the overall iterations for the project at the project level.
At the team level, you set the team's backlog iteration and what sprints belong to that team.
If the project level iteration is just for rolling up the progress of the individual teams, then yes, you can remove the project level iterations.
When creating a new Snapshot what difference does checking "Create new baselines" make ?
If this is unchecked, a snapshot is created and all components in the snapshot are backed up and so created baselines ?
If this is checked then new baselines are created but they also seem to be created when "Create new baselines" is checked.
As per this thread
A snapshot is just a set of baselines (each baseline from a different component). It's what ClearCase would call a "composite baseline".
You can snapshot the state of either a workspace or a stream, whichever you prefer. That will automatically create baselines when needed, i.e., when the current configuration of a component in that workspace/stream is not currently captured in a baseline
So, as mentioned in this thread
When I create a new snapshot, it only create new baselines in changed components, not in components have no changes.
I suspect checking in "Create new baselines" will force the creation of baselines for all components, including the ones which were already at baseline.
That enforces consistency in the name of the baselines included in the snapshot.
Update Jan. 2018, 3+ years later: Dmitry Grigoryev mentions in the comments:
the label on that checkbox is much more clear in newer releases now
I am getting this error when trying to merge TFS2008. There are no pending changes on either source or destination branches.
TF14083: The item {0} has a pending merge from the current merge operation, please resolve and check in the current merge and merge again to pick up this change.
There is a "Resolve Conflicts(x)" link at the top of the pending changes window that I missed.
Did you read this article?
One of the suggestions there is to try the operation in a new workspace.
Also, if you have renamed or deleted one or more branches/folders, there might be changes in your workspace you're not aware of. Is there anything (even outside the source and target) in your Pending Changes window?
Here's a work-around worked for me.
Short version: Merge all files that don't report TF14083 first and check in changes, then perform a remerge.
Long version:
We had no files in shelves or not checked in, but when trying to perform a merge from one branch to another I got the error message TF14083: The item '' has a pending merge from the current merge operation, please resolve and check in the current merge and merge again to pick up this change.
My workaround was to merge all other files except those reported with a TF14083 error. Check in that merge, then perform a new merge from and to the same branches as previously, and now TFS picked up the changes in those files reported with TF14083 in the previous merge operation and merged them with no warnings or errors.
Go figure!