is there a way to add custom workflow to "Create new project" screen?
http://s13.postimg.org/f1acwcerr/Untitled_1.jpg - create new project screen
Or make my custom workflow to be default, but seems that it's not possible at the moment.
The problem is that I created a workflow that suits my needs better than those which are available by default at marketplace. I would like to use this workflow as default for all projects. Or have an easy way to create a new project based on my custom workflow.
Thanks
There is no way to set a user created workflow as the default but there is a issue opened with Atlassian created about it. (See JRA-9363)
Your only option would be to create the project and then immediately change over its Workflow Scheme to be that of your custom one that has the custom workflow associated to it.
Related
I am setting up a Project on Visual Studio Team Services.
On overview page, It has a project logo at the top left, it's seem create by a short name of full project name. I want to change this icon to own logo, but I has found no way to change it. Would you please help me let me know can we change this icon, if yes, how can I do this?
It looks like this functionality was removed as part the new navigation.
You can vote to have the feature added back here:
https://developercommunity.visualstudio.com/content/idea/366277/change-project-icon-in-new-navigation.html
The best answer I found for Azure DevOps Server was to update the default team icon and perform a force-refresh (CTRL+F5). It appears a similar capability is on Azure DevOps Services.
Source: https://developercommunity.visualstudio.com/comments/960724/view.html
This functionality is rolling out with the current deployment on VSTS. See the section "Custom Project image on Project description page" in our release notes at Streamlined code and work items search – VSTS Sprint 124 Update:
VSTS has allowed you to upload a custom image for your Project (and
default team) for some time. However, this image was only visible on
the settings page. With this update, you will see the customized image
on the description page, which helps to give a unique identity to a
Project. If not customized, you will see an auto-generated image based
on the Project's name.
Take your project link (ex: https://xxx.visualstudio.com/RobocopProject) and append a /_settings to it, on the resulting page the icon will be clickable and editable.
I have created a custom workflow where tickets or issues are submitted then the order of workflow steps is:
review (ALL)
business justificatioN
in progress
verification (ALL)
deployment
testing
done
ON HOLD (ALL)
RETIRED (ALL)
I created the custom workflow by making a copy of the default workflow with TODO IN PROGRESS, and DONE Status however when you go to edit an issue in my custom workflow you still have the option to change the status to TO DO (from the default workflow) even though my custom workflow is clearly the one which is selected for the Scrum project.
What do I need to modify so that the TO DO STATUS from the default workflow isn't showing up at the top of my issues.
For example if an issue is created using the custom workflow the STATUS defaults to REVIEW as expected as it is the first step in the workflow. When trying to transition it to the business justification step while viewing the issue a STATUS of TO DO is visible.
How can I remove the option to change the status to TODO given it is not part of my custom workflow which is applied to the project and is instead part of the default workflow.
Can I remove the default workflow for the project? to achieve this (I am not sure how to completely remove the default workflow) so far I have only been able to assign my own.
This is possible if either:
The TODO status is still used in your custom workflow.
You're looking at an issue that does not use your workflow. This is possible if your "Workflow Scheme" is not configured correctly. A project has a "workflow scheme" that can contain multiple "workflows" for different "issue types". You can review these settings in your project's settings. The documentation is available here.
I want to change authentication of an existing project but I can't change it. Because, I couldn't find the "Change Authentication" button which exists during new project setup. Please tell me, how can I change authentication of existing project?
I think you cannot change that via a push off a button.
Perhaps compare two sample projects with the existing and desired authentication?!?
Is anyone aware of a way to define a set of default issues, which can then be attached to a project type definition so that each time a project of this type is created, it comes with these issues?
All of our projects have issues like 'create wireframes','set up local environment' etc. and I'm looking for a quick way to automate this part of project setup.
I have full admin access and I can't see anything in the issue or project setup that does this.
Can't you just create a set of issues in an empty project and export them?
You can use that set and import it into your new project to start with.
In JIRA, what is the appropriate procedure to add a Workflow to a Workflow Scheme?
In my case I created a new Issue Type which is referenced by a newly created Workflow. In order to add the Workflow to a Workflow Scheme, the Workflow Scheme must be Inactive. In order for the Workflow Scheme to be Inactive, I have change each Project's Workflow Scheme to something else. Only when there are no Projects using the Workflow Scheme can I edit it.
When changing a Project to a different Workflow Scheme ("Associate Workflow Scheme to Project"), JIRA warns that a backup should be made and that every single issue will be changed. Something tells me this is an overkill for such a simple change. I really don't want to alter every issue just to add a new Workflow to a Workflow Scheme.
Am I missing something?
Follow up: According to Atlassian, there's no choice but to migrate to the new Workflow Scheme.
Go to Admin, Schemes, Workflow Schemes. Copy the Workflow scheme currently in use by your project. Edit the copy and assign the new workflow to the issue type. Then go back to the project and select the new workflow scheme, which may prompt you about migration of issues if necessary.
It's not overkill, it's just being careful. You don't actually change anything unless you have to, for example if there are issues of the new issue type in the project.
~Matt