...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
On this page: |
|---|
...
| Anchor | ||||
|---|---|---|---|---|
|
Question
How to completely remove Timetracker from a certain work item? (If the Timetracker tab is missing or you don’t see the button to track time, then implement the described procedure in reverse order)
Answer
This can be worked around by adjusting a layout of a given item type in Azure DevOps settings (Organization Settings -> Boards -> Process -> [Process name] -> [Item type name]). There, you can hide 7pace Timetracker controls on item level (1); or even the whole 7pace tab (2). Just consider the fact that removing 7pace tab (2) will also strip you of the beneficial insights available directly on an item, so I would recommend hiding the Timetracker section on Item detail (1) only.
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Unfortunately, when you migrate from DevOps Server to DevOps Services, extensions are not inserted into the work item form template (it is marked as modified internally in DevOps Services). Therefore, you have to modify your WI xml templates in order to add 7pace Timetracker-specific fields like the "7pace Timetracker" tab and "Start Tracking" button on the work item form.
The basic process is described here: https://docs.microsoft.com/en-us/vsts/extend/develop/configure-workitemform-extensions?view=vsts
In this specific case, do the following:
1. Navigate to "https://dev.azure.com/[youraccount]/_admin/_process".
2. Locate the process template you want to modify, click on "..." button and Export it. This will produce a zip archive with a lot of folders and files inside.
3. Open the "WorkItem Tracking\TypeDefinitions" folder. There, you should see a lot (10-20) of xml files of Work Item Types.
4. Select the types you want to have "Time" and "Work" added to the work item form (or maybe all) and apply edits to each xml:
a. Add this into your <WebLayout> as the first element:
<Extensions>
...
<Extension
...
Id="7pace.Timetracker"/>
</Extensions>
b. Add two (2) new groups to enable "Time" and "Work".
Work is located by default (but you can change the location as you wish) inside <Page> second <Section>, before closing </Section> add:
<GroupContribution
...
Label="Work"
...
Id="7pace.Timetracker.work-item-form-group"
...
/>
Time is a "page", add it after </Page>:
<PageContribution
...
Label="Time"
...
Id="7pace.Timetracker.work-item-form-page"
...
/>
Apply the same edits to all affected xmls.
...
| Anchor | ||||
|---|---|---|---|---|
|
Question (on-premisepremise only)
I was installing 7pace Timetracker for DevOps 2019 and after the installation of work item form contributions, I received an error message that installation had finished, but with errors.
Answer (on-premisepremise only)
DevOps issues an error when Boards have been disabled for a project and you try to install work item form contributions.
Here is the error message you will see in the log if this is the case:
[Error found in log] Message: VS403121: Extension(s) "7pace.TimetrackerOnPremises" does not exist or has no work item form contribution.
If you see this error message in the log, please first check to see if Boards have been disabled for your projects.
...
The screenshot, above, shows the list of enabled features for projects, including Boards. If the error message in question displays after installation and you have Board disabled for projects, rest assured, your work items form contributions been installed correctly to your projects.
| Anchor | ||||
|---|---|---|---|---|
|
...
We have TFS 2017 update 1, and on-premise Timetracker for TFS, but we don't see the “Time” tab on TFS Epics, Features, Stories and Tasks. How do we enable the "Time" tab on the work item form?
Answer (on-premise only)
This is a known issue in TFS 2017 - TFS has recently updated the work item dialog form and users can choose to use the old or new form. Unfortunately, the "Time" tab won't work on the old work item form, which is why you don't see it. We currently have this in our backlog and will update you when we implement it.
...