I accidentally created an issue when setting up my first board. I have no need to delete the Issue - it has nothing attached to it. But I just want to keep my board clean.
Is there a way to actually delete this issue?
A little bit late to the party, but according to ZenHub docs
It is not possible to delete a Release once it has been created.
Closing a Release will remove it from your Board and filters. This
release will only be visible to users scrolling through the list of
closed releases in the Release report tab.
Related
I have lots of old and useless notifications when I mark them done they go to "done" section (obviously) but I couldn't find a way to remove them completely. How can I remove these old notifications from my life?
There does not seem a way to manually clear out the Done section.
The documentation simply mentions:
Notifications marked as Done are saved for 5 months.
So they are cleared out eventually, but not immediately.
On the Azure DevOps TaskBoard for a sprint, it would appear that the only thing I can drag across the board is Tasks. Not bugs. Not Backlog items. Which means if I want to see where a bug is on the board, I have to create a task for it. (Note: My project uses Scrum. Bugs are managed with requirements)
I guess this makes sense. It is a "Task board" after all. But this seems tedious. Most of the time, the bug is the task. I make a bug, make a check in, and mark it done. I would expect to be able to drag the bug itself across the board to mark it done.
And even if I go to the trouble for creating a task for a bug (or a Backlog Item) and then I drag the task across the task board to "Done", the bug's status still stays where it was. It doesn't change to not done. I then have to go to the bug and manually mark it as "Done"
This really limits the usefulness of the Taskboard for our planning.
Am I missing something? Is there way to change this?
You can choose to manage the Bugs with tasks as Daniel commented. And You can use extension Work item form one click actions to assign the Bug to some parent PBI automatically. See below example:
First you need to install Work item form one click actions extension to your Organization.
Then Go to project setting page-->WIT One Click Actions under Extensions-->Bugs-->Create rule group-->New Rule
Triggers: New work item load
Actions: Link to an existing work item(relation type: Parent; Work Item id: Id of PBI)
After above rule is created. The newly created bugs will be automatically added to the parent PBI you specified in above rule.
However, The PBI and Bugs(managed with requirements) can be moved around in Boards. So you can use the filter to view your work items in a specific sprint.
Sourcetree 3.3.6 with windows 10 not updating UI contents or not refreshing views.
If you want to see updated view then you need to restart app.
any solution for this?
Pressing F5 after fetching, making edits, etc. to refresh updates the UI. Annoying, but usable until fixed.
seems to be related to bookmarks. deleting it solves it, at least for me.
found it here: https://community.atlassian.com/t5/Sourcetree-questions/Manual-refresh-required/qaq-p/1256362
how to delete bookmarks can be found here:
https://confluence.atlassian.com/sourcetreekb/bookmarks-column-repository-browser-overview-781398414.html
I have been tasked with running point on implementing Azure DevOps on my team at work.
We are using the CMMI process and tracking bugs at the requirement level.
Recently, it was brought to my attention that when we marked a Bug work item as active, manually change the state and not drag the card to the next swimlane, it simply disappears from the board. The work item can still be viewed on the task board, but is no where to be found on the requirements board until the state is changed again.
Has anyone else run into this problem and know of a fix?
Thanks
The issue is the configuration of the board itself. The default does not include bugs, so when you create your columns, the bug configuration for "Develop" gets set incorrectly.
Go to your settings for your board by clicking the gear icon in the upper-right of the board
Once into the settings, choose "Columns" from the list of items on the left of the modal window and then choose the column where the Bug items keep disappearing (the Develop column in my case), and you'll see some drop-downs for Bugs and Stories for "State Mapping".
If you change the bug setting here to "Active" and then save, the bugs should reappear on your Develop board. You'll want to do the same check for any other columns.
You can update Working with bugs setting for boards to Bugs are managed with tasks.
You will need team administrator or a project administrator permissions to change this setting:
I've recently started on a new project with a new firm. The release pipelines, in particular, the release view, is completely different, AND it doesn't work properly. The logs don't load, hardly any of the links work and it doesn't support themes correctly.
Does anyone know how to change it back? I've looked under preview for not only my user but the whole organisation and I don't know what is going on.
The first image is what I am after...
This is what I currently have...
Thanks in advance
They have their account feature flags set to use the old release view. You can override that at the user level by going to "Preview Features" and turning on "New release progress view".