Skip to content

Commit

Permalink
Merge pull request #59 from ALM-Rangers/feature/upgrade-to-new-sdks
Browse files Browse the repository at this point in the history
migrate extension to new skds
  • Loading branch information
MOlausson committed Mar 23, 2022
2 parents 8ad55a0 + 8d9be4d commit 77e9721
Show file tree
Hide file tree
Showing 61 changed files with 7,756 additions and 13,545 deletions.
4 changes: 3 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -19,4 +19,6 @@ css/
**/out/chrome
npm-debug.log
debug.log
~$*.pptx
~$*.pptx

.vscode
3 changes: 2 additions & 1 deletion .vscode/settings.json
Original file line number Diff line number Diff line change
Expand Up @@ -10,5 +10,6 @@
"**/out": true
},
"files.trimTrailingWhitespace": true,
"typescript.tsdk": "./node_modules/typescript/lib"
"typescript.tsdk": "./node_modules/typescript/lib",
"eslint.alwaysShowStatus": true
}
26 changes: 16 additions & 10 deletions .vscode/tasks.json
Original file line number Diff line number Diff line change
@@ -1,30 +1,36 @@
{
"version": "0.1.0",
"version": "2.0.0",
"command": "cmd",
"args": [
"/C"
],
"isShellCommand": true,
"showOutput": "always",
"suppressTaskName": true,
"tasks": [
{
"taskName": "Run Dev",
"label": "Run Dev",
"type": "shell",
"args": [
"/C",
"npm run dev"
]
],
"problemMatcher": []
},
{
"taskName": "Package Dev",
"label": "Package Dev",
"type": "shell",
"args": [
"/C",
"npm run package:dev"
]
],
"problemMatcher": []
},
{
"taskName": "Package Release",
"label": "Package Release",
"type": "shell",
"args": [
"/C",
"npm run package:release"
]
],
"problemMatcher": []
}
]
}
11 changes: 5 additions & 6 deletions configs/dev.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,6 @@
{
"public": false,
"baseUri": "https://localhost:9090",
"name": "Dev: Azure Boards Kanban Tools",
"publisher": "chrismason",
"version": "0.0.2"
{
"public": false,
"baseUri": "https://localhost:9090",
"id": "kanban-board-tools-dev",
"name": "Azure Boards Kanban Tools (dev)"
}
8 changes: 5 additions & 3 deletions configs/release.json
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@
{
"public": false,
"publisher": "alm-rangers"
{
"galleryFlags": [
"Public"
],
"public": true
}
5 changes: 5 additions & 0 deletions configs/test.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
{
"public": false,
"id": "kanban-board-tools-test",
"name": "Azure Boards Kanban Tools (test)"
}
92 changes: 46 additions & 46 deletions marketplace/overview.md
Original file line number Diff line number Diff line change
@@ -1,47 +1,47 @@
# Azure Boards Kanban Tools

This provides a set of tools to enhance Kanban board usage within Azure DevOps and Azure DevOps Server.

# Copy Kanban settings
With Azure DevOps, we see more and more teams switching to a single team project approach with teams being split based on a combination of iterations and areas. This can result in dozens of teams set up within the system. Once a team goes in and configures their Kanban board with their settings: card rules, swimlanes, column definitions, etc. they may want to share that setup with other teams. This extension allows teams to either grab settings from another team and apply them to their boards or to allow a team to copy their settings to another team.

## Getting started

1) From the Work hub, navigate to a backlog level such as *Epics*, *Features*, or *Backlog items*.
2) From the backlog level, switch to the Kanban board view.
3) Click the icon to launch the Azure Boards Kanban Tools dialog by clicking on the brush icons.
4) Use options within the dialog to select the team to copy settings from or to another team.

In this release, the following configurations will be copied for each backlog level within the process template:
* Board card rules
* Board card settings
* Columns within the board
* Swimlanes

### Advanced usage

When you select a team to copy settings to / from, we will need to move work items in the current Kanban board to new columns. With this extension, before you do the copy, you will have the ability to optionally configure how that mapping would be applied. Otherwise we will move work items to the first column that matches the work item's current state. To do so, click on the **Customize column mappings** button on the dialog.

# Known issues

In this current version of the extension there are a few known limitiations and issues.
* **Work item histories may be modified** - If you have work items on your target board you may notice that work items may have additional history states added to them after copying indicating column or swimlane changes.
* **Work items may move to a new swimlane** - If you have work items spread across multiple swimlanes on your target board, those work items may be moved back to the "default" swimlane after settings are copied to that board.
* **Additional backlog levels may be created** - When copying settings from one team to a second team, if the team copying settings from has more backlog levels visible than the destination team, additional backlog levels will be created on the target team.
* **Task level settings are not copied** - The settings are only copied from any portfolio backlog levels as well as requirement backlogs. Backlogs at the task level are not supported at this time.

# Learn more
The source to this extension is available. Feel free to take, fork, and extend.

# Contributors

We thank the following contributor(s) for this extension: Edward Fry, [Jesse Houwing](https://github.com/jessehouwing), Chris Mason, Gregory Ott, Tiago Pascoal, Prasanna Ramkumar, Kees Verhaar.

# Feedback

We need your feedback! Here are some ways to connect with us:

* Add a review.
* File an issue on [GitHub](https://github.com/ALM-Rangers/azure-boards-kanban-tools/issues).

# Azure Boards Kanban Tools

This provides a set of tools to enhance Kanban board usage within Azure DevOps and Azure DevOps Server.

# Copy Kanban settings
With Azure DevOps, we see more and more teams switching to a single team project approach with teams being split based on a combination of iterations and areas. This can result in dozens of teams set up within the system. Once a team goes in and configures their Kanban board with their settings: card rules, swimlanes, column definitions, etc. they may want to share that setup with other teams. This extension allows teams to either grab settings from another team and apply them to their boards or to allow a team to copy their settings to another team.

## Getting started

1) From the Work hub, navigate to a backlog level such as *Epics*, *Features*, or *Backlog items*.
2) From the backlog level, switch to the Kanban board view.
3) Click the icon to launch the Azure Boards Kanban Tools dialog by clicking on the brush icons.
4) Use options within the dialog to select the team to copy settings from or to another team.

In this release, the following configurations will be copied for each backlog level within the process template:
* Board card rules
* Board card settings
* Columns within the board
* Swimlanes

### Advanced usage

When you select a team to copy settings to / from, we will need to move work items in the current Kanban board to new columns. With this extension, before you do the copy, you will have the ability to optionally configure how that mapping would be applied. Otherwise we will move work items to the first column that matches the work item's current state. To do so, click on the **Customize column mappings** button on the dialog.

# Known issues

In this current version of the extension there are a few known limitiations and issues.
* **Work item histories may be modified** - If you have work items on your target board you may notice that work items may have additional history states added to them after copying indicating column or swimlane changes.
* **Work items may move to a new swimlane** - If you have work items spread across multiple swimlanes on your target board, those work items may be moved back to the "default" swimlane after settings are copied to that board.
* **Additional backlog levels may be created** - When copying settings from one team to a second team, if the team copying settings from has more backlog levels visible than the destination team, additional backlog levels will be created on the target team.
* **Task level settings are not copied** - The settings are only copied from any portfolio backlog levels as well as requirement backlogs. Backlogs at the task level are not supported at this time.

# Learn more
The source to this extension is available. Feel free to take, fork, and extend.

# Contributors

We thank the following contributor(s) for this extension: Edward Fry, [Jesse Houwing](https://github.com/jessehouwing), Chris Mason, Gregory Ott, Tiago Pascoal, Prasanna Ramkumar, Kees Verhaar.

# Feedback

We need your feedback! Here are some ways to connect with us:

* Add a review.
* File an issue on [GitHub](https://github.com/ALM-Rangers/azure-boards-kanban-tools/issues).

Review the [list of features and resolved issues of latest tools and extensions](https://aka.ms/vsarreleases) for information on the latest releases.

0 comments on commit 77e9721

Please sign in to comment.