|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Jeff Turner [Atlassian] - 13/Jan/05 12:28 AM
Currently the workflow is set on the project page. How about if we let users select the projects on the workflow scheme page? This would let one bulk-associate a group of projects with a scheme.
Yes, this would be VERY helpful! The way I work it is that we have a workflow that we like for all projects. To improve or change the workflow I copy it, make the change and then I have to move each project into the new workflow one-by-one. It takes a while.
I like the copy, change, move because I can make the change, move over a couple projects to test it out and then once I'm comfortable, move the rest of the projects. Then I can always fall-back to the previous 'version' of the workflow if something is wrong. So just a bulk move feature would be nice. I have added JIRA-9096 which includes this issue as well as my other major workflow annoyance: The fact that you have to create copies of workflows and schemes in order to do anything. The height of tedium.
The more projects we have, the more annoying this requirement is. I need to make a small change to the workflow, and I am in the middle of switching 20 projects over to a new workflow. Seeing as our current live issue tracking software has over 2000 projects, this will swiftly become impossible.
We really need a way to either: David,
We want to do the editing of live workflows real soon. That is about as much as I can say at the moment. Cheers, I agree with everyone that has commented. The task of editing a workflow is a real pain currently. Either make it where workflows can be edited live or make it easier to copy projects to another workflow scheme. I understand the concern with editing live workflows. Maybe provide a way to "lock" the workflow while it is being edited. Just a thought.
Agree with all comments.
We only have about 12 projects and constantly copying and re-assigning is annoying. Modifying live workflowswould be great, as would an easier way to assign schems to projects. I personally find the schemes more annoying than useful, just another item to copy, rename then activate. It might be nice to revert back to a similar more like before schemes were introduced, it was esier back then for smaller numbers of projects. Same here. I administer a JIRA application with > 100 projects. When our QM folks demand a change for the workflows due to SOX, ISO9000 or other things that make our life a pain, this means for me a complete weekend shift in order to apply the new workflow to all projects. I wish I could hit ONE button Friday evening and check the results on Saturday morning. Either this or make the workflow changes much, much faster...
Best regards, sorry if my first comment seemed a bit rude but I am going to be administering over 200 projects, most of which use the same workflow and I am still in eval mode!! I find it really hard to believe that this reuqest has been open for as long as it has and there hasn't been any progress on it !!?? If critical issues are going to be open for two years and still not get any focus, it certainly raises my concern when considering support prior to purchase.
Not trying to be mean just honest! Thoughts?? -Cheryl M I agree completely. I think if everyone watching and voting starts being a little more active here, we might get some attention. Our contract is up for renewal soon, and this issue is one major factor in my decision. I love Jira otherwise, but if the issues we need don't get fixed, then we just may stay on the version we've got.
Perhaps someone from Atlassian could comment on this for us?
I'm guessing it's not a minor patch - but some idea of an expected release would be useful. Hi,
Thank you for your comments. May I ask if you believe that implementing Having said this, unfortuantely, I do not have an actual implementation date for this feature (or We would be very interested to know your thoughts on implementing Cheers, I actually think they are almost duplicates.
The main pain is that we can't edit active workflows. Addressing Yes, that
Yes, please. We have on startup of jira 50 projects and the grow more and more.
A published workaround for this issue would suffice as a starting point. Is there a way that the update can occur by bypassing the Jira user interface and making a change direct on the filesystem while the server is down?
So when do you think this feature will be available? I see in the comment that this feature is asked since 2005. I hope this will be available soon. Today, I will have to change the workflow scheme for about 49 projects and the workflow did not change. I just add 2 issue type to a new workflow scheme because I can not add it to the current workflow scheme.
Hi Mathieu,
At the moment, unfortunately, I do not have an implementation date for this feature. We are looking at implementing Cheers, In my world, the priority of this should be higher than Minor. We have over 200 projects, so every time I make a workflow change, I have to go through 200 manual steps.
What makes this worse is that we have 23000 issues, and because of the processing time required to update every issue to the new workflow, I can't just quickly plow through the 200 projects; on some projects, I have to wait 1 or 2 minutes. As a result, it can literally take HOURS of clicking to do a workflow change. I can parallelize it by opening 10 or 20 tabs at once in Firefox, but I still don't think it has ever taken me less than 1 hour. If I could do it in bulk, I could at least click the "go" button and then come back later when it completes. We would love to see this implemented as well! We have many many projects using just a few workflows, and it would cut workflow maintenance time by 90% if I could bulk migrate projects to a new workflow. We're running JIRA Enterprise 3.12.2 with a Commercial license. I would LOVE to see this scheduled for 4.0, if not sooner.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Minor
Change workflow scheme for multiple project at the same time
