I have created a workflow of changing status in JIRA but now I want some of the statuses to be deleted. It does not give me the option to delete. I read in the document that you cannot delete active workflow steps.
How can I inactivate a workflow is not described anywhere. I have spent hours on it.
I'm not sure I got you 100% right, but to delete a workflow you have to unassign it from the workflow scheme, which is only possible if that scheme is not used by any project. If a status is not used anymore in any workflow it can be deleted if I remember correctly.
How I do it in most cases is: I create a new workflow, as it is needed. Then I associate it to the project. Afterwards I can delete the old one.
Related
I am trying to automate my project boards. I would like an action to trigger when someone opens a Pull Request and links it to a issue on the board, then the issue would be moved to "In Review".
I imagine once I trigger by a pull_request, this information would be seen on the given environment variables. But I dumped all of them and I could not find any reference to the issue I am linking and would like to move on the project board.
Can someone give me some light on what I could do to achieve this result?
First you can reference an issue in your commit message described in the documentation. Then you can set up built-in automations for the project board. If you then push something to your repository and create a merge request, the issue should be automatically linked and moved to the column "In Review".
If I submit a pull request to Github with some changes..
And then someone edits those changes..
And I approve those changes to my PR..
And then want to make one more change to the same file..
If I go to edit the file (on the patch branch), I can see the proposed changes I have made, but not the ones I approved from the suggestions the other person made..
This makes it very confusing to know what is going to happen when the PR is accepted (if I add more changes), will the other User's changes get lost? are they added as separate patches? I'm not sure how to test this out other than setting up another github account and trying to recreate the scenario, but maybe someone can answer before I try that.
I'm running builds with AzureDevops piplines. When I'm creating new pipline I'm not queueing it and just saving. If CI trigger is selected pipline will run if anything is checked in.
But on the very first run/chack-in pipline will be liked (associated) to ALL check-ins (changesets/commits) that happened before the current one and to all workitems of those chack-ins.
This behaviour is not desired for me. Is there a way to disable it?
On all subsequent check-ins build will be associated only with the one that triggered the pipline. And this is what I want for the first build as well, for it to be associated only with the chack-in that triggered it.
Without seeing exactly what's happening, it's hard to provide advice. It could also behave differently if you're using Git or TFSVC variants. Here's a few things to try:
Disable the CI trigger, do your first check-in, then re-enable the trigger. That might skip the change-set and work item affiliation one time.
Delete the offending build after it runs or do the laborious task of manually deleting all links in it.
If you're using Git, you can also limit the CI trigger by using a Pull Request with Squash merge. This will consolidate the commits down to one.
There isn't the way to disable it. It would compare previous run, then include all changesets between them. So, for first run, it must includes all previous changesets.
You may create a new branch for a folder, then configure build for that branch. Learn about branching strategies for Team Foundation Version Control (TFVC) and how to select an effective strategy
I did some tests with Actions on Google but it was with the wrong account so I deleted the project. Once I created the new one with the good account, I discovered that the invocation isn't deleted so I can't use it anymore.
Did I miss something to get it completely deleted?
I've received the mail about the 24h hour to recover the project but it's been more than 24h now.
This happened to me. Support told me that there was a way to "undo" the project deletion and once un-deleted I could change the name so that the old one could be re-used. I forget the details but that option wasn't available for me. They told me I could wait a month or so until the project was physically deleted from their cloud or I could submit a ticket to delete it and wait a week. That's what I did.
I have a basic scheduled workflow that creates issues, but can't get the flow to trigger as it should on the projects to which it is attached:
I have 3 projects: A, B and C
I have a scheduled workflow that creates a single issue (summary and description only) in each of A, B and C.
When the workflow is attached to project B, it triggers and all 3 issues are created.
When the workflow is attached to A and/or C, the workflow does not trigger.
Many of the project fields overlap, but given that I'm only setting the summary and description, i don't see that being a problem?
I can't find where workflow execution gets logged, so don't know if there are problems (but the flow does execute on project B)...?
Any help appreciated!
Be aware that stateless and state machine rules are executed on behalf of a user who actually made changes that triggered a workflow. Scheduled rules, in turn, run on behalf of their author. Thus, make sure the author has respective permissions in all of the projects the rule is attached to.
Although not an answer to the problem, this problem was resolved by upgrading from YT5 to YT6.
Part of the upgrade involved going through this problem: http://forum.jetbrains.com/thread/YouTrack-1810 (resolved by backing up, uninstalling YT5, removing all YT folders, then installing YT and restoring backup)
That leads me to wonder if the problem wasn't related to a bad/locked/corrupted file somewhere in the YT directory?
Nevertheless, post upgrade, I attached the scheduled workflows as they were and they fired without hindrance.