I created a webhook for "Jira / Microsoft Teams" integration.
We need to get updates on anything happening on "bug" issues (creation, updates) into a Teams channel.
We created this JQL:
project = General AND issuetype = bug AND status changed
But this is just for the status and does not support anything else (creation, updates in other fields etc.)
Unfortunately I cannot use the checkbox options either because I have no way to choose the equivalent of issuetype = bug there.
I assume that the only way is JQL but I cannot find a way to describe "report all changes in the bug", plus I did not see it working even for the status change I reported above.
Is there a solution to this?
Thank you.
UPDATE: If I combine both like that, it seems to partially work. Partially because changes in the Description are not triggered, etc. How can these be triggered too? (i.e. EDITS in Description, etc.).
Related
Assume the following build
Powershell Task Write-Host 'Original1';
We create the following draft
Powershell Task Write-Host 'Original1';Write-Host 'Draft2';
At the same time we had to change the original build - set Continue on Error, for example, and a new Timeout value.
Then we publish the draft. The original build would become
Powershell Task Write-Host 'Original1';Write-Host 'Draft2';
But both Continue on Error and Timeout would be overwritten with the values from the draft (original values at the time the draft had been created).
Perhaps I am missing something in my understanding how drafts should work (there is basically nothing about them on https://learn.microsoft.com/en-us/), or perhaps it is even a genuine defect in the TFS version we use (2018.2), but I'd have expected either a proper merge or at least some message preventing one from overwriting the changes in the original build.
Otherwise drafts just seem to be of very limited and error-prone use.
Am I missing something?
P.S.: Tried different combinations of changes on multiple tasks and etc. In some cases(when modifying inline powershell in the same task) drafts got "published" (as deleted), but no changes at all made their way to the original build (not even a new history entry), so I am much more inclined to think that the entire drafts feature is a bit defective as of now
We have contacted Microsoft and as of now (end of 2018) the current behaviour is considered to be by design
As it turns out, as of now this is the intended way for it work. The
Draft option just exists so that you can first test a definition
before committing it.
So, until something changes, the Drafts feature should be used carefully in any environments where concurrent changes to(drafts of) builds/task groups/releases can be made.
We've got TFS email alerts set up when certain files are changed. In the future, many of these files will likely have "copies" via branching. Other than manually creating additional alerts each time a branch is created, can anyone offer some strategies for this scenario? Or simply strategies to make sure we're covered in case a branch is created and we forget to create these alerts.
Thanks for any help!
There is no out of box feature for this, you can submit a feature request on VSTS User Voice.
However, if the name of the files is unique，you can create an email alert just with "File Name = filename.extension" and "Folder Path Contains XXX". This will track the change for the file in the specified folders/branches.
I want to prevent my users from logging work once an issue gets to a particular status. How can I accomplish this?
I have a post-function in my workflow that sets the Resolution, but the "Log Work" item in the More menu still shows up.
I don't see in the Project or System administration any options about it.
You can accomplish this by setting jira.issue.editable to false in the properties of the status in the workflow.
Find the active workflow that applies to the issues you wish change. This is most easily done by either: going to the 'Workflow Schemes' admin page, then clicking on the Workflow link in the row applying to the issues' project and issue type, or clicking View Workflow in the Issue View.
To edit the workflow, you will need to either create a copy of it (if using the default jira system workflow) or edit the draft of the workflow.
In the Workflow Editor, for the 'Closed' step, click View Properties (in Text mode) or Properties (in Diagram mode) to see the step properties.
Editing issues in the selected step is enabled by default, or you will see a jira.issue.editable property with value true. Either create the value or chang the property value to false.
Publish your draft workflow, or if editing a copy, activate the workflow by creating a new workflow scheme associated with the edited workflow, and then associating it with your project.
Reference: https://confluence.atlassian.com/jira/allow-editing-of-closed-issues-138704.html
In my implementation of JIRA, I have a custom field called Developer which gets populated automatically (username) whenever someone move the JIRA from Open to Fixed state. Now I want something similar for the Fixed to Reopen transition. That is, whenever the tester changes the status to Reopen, it should go back to the Developer or the Project Lead (in case the field isnt populated as the custom field can be overridden).
I tried to implement a post function, but there isn't a way where I can use OR criteria. Or is there a way?
You can do a Post Function on the transition using the Script Runner plugin if its a self-hosted JIRA instance which will allow you great flexibility in the logic to fill the target field in.
I finally managed to find a workaround for this.
Download the Workflow Enhancer for JIRA plugin (FREE). You would also need JIRA Suite Utilities (I had it installed already for some other customization)
In the Fixed to Reopen transition, add a Post Function and use Copy Value From Other Field to update Assignee from Developer field
Then add another Post Function underneath this where you need to use Universal Post Function. Here make the boolean condition as {Assignee}=="" and select Choose post function to execute: as Assign to Lead Developer
Publish the draft.
Whenever i edit the subtask issues the screen sets the assignee's value from reporter field.
for ex: if reporter is xxx and assignee is yyy . When i edit this sub-task issue the screen shows that assignee=xxx.
Any solution for this?
Not sure why this happens to you, i tried to reproduce it but works fine for me.
Do you have any plugins? any custom field scipts? any post function script?
Anyway, you can solve that by one of the following ways:
Post function script as explained here
Plugin like Behaviours Plugin or Jira Scripting Suite
Add a custom filed, edit it's description and add a jQuery script that will set the assignee option
If you need any help or have question on any of the solutions feel free to ask.