Azure.el

Requirements

Emacs 26.2 or later and pandoc.

Installation

(use-package azure
  :config
  (let ((token-file (expand-file-name "~/.azure.plstore")))
    (setq azure-access-token-file token-file
          azure-organization "your-organization")
    (add-to-list 'org-agenda-files (expand-file-name azure-cache-directory))
    (azure-minor-mode 1)))

(use-package azure-devops
  :after azure)

Usage

In order to make requests to Azure’s API, you will need to set an organization, a project, a team and an access-token. You can set all of the above via the command azure-init. The token will need access to the scopes listed below to function properly. Note that Azure.el is in early stages and that the scope could increase with time, possibly making it neccessary to generate a new token.

vso.work_write

azure-devops-search

This is the main entry-point when using azure.el. It brings up a search-buffer, where you can list and find work-items via different criteria. Wether you are assigned to the work-item, wether it is in progress etc. Clicking an item, brings up a buffer of the work-item at point.

azure-devops-work-item

The work-item buffer is an org-mode buffer, so you can edit it as usual and clock-in to the task etc. Typically, this is run when clicking a work-item from a search-buffer, but you could also quickly find a work-item by searching for it in the mini-buffer by name or exact id. In addition to the properties available in Azure’s UI; like comments, effort etc. there’s an additional section for personal notes. These are notes that are not part of the synchronization that happens upon save and thus can only be viewed from your local machine. As briefly mentioned, the work-item is updated upon save. This is a synchronous event where the task-issue will be reified with whatever is on the server. That means that upon save, the file you just saved will be updated with the “truth” from the server. Note that some UI-jumps are to be expected in this situation.

azure-devops-work-item-create

With this command, you will be prompted to input a title. Once a title is supplied, a work-item is created on the server and the new item is visited via azure-devops-work-item. At this point, it’s just about editing and saving the changes.

Working with org-mode & git

So this is where the pieces all falls into place! Say you’ve done some work on an item that you are clocked into. You are ready to commit and have a commit-message prompt open. By evaluating org-clock-goto, you can see the work-item and all the discussion about it. Oftentimes I can use the body and title of the work-item as commit-message and if not, I tend to have drafted something in the personal notes section that would suffice. I’ve found that writing such commit-messages upfront, helps me keep each commit more focused.

Contributing

My ambitions for azure.el is just to cover my day to day usage of Azure’s functionality, but you might set the bar higher and want to contribute. If you find a flaw or something that’s not quite optimal, you can file an issue, but code-contributions are more than welcome as well. Just note that all contributions should happen in azure.org and not azure.el and that the outline reflects Azure’s documentation to some degree, making it easier to keep track.