Index
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
簡易ワークフローとは
Every board represents one or more projects, and every project uses either a JIRA Workflow or a Simplified Workflow to control the transitioning of issues from one status to another. The workflow determines which statuses are available.
If your project was created together with a board via the GreenHopper 'Getting Started' page, it will probably be using a Simplified Workflow. If your project was created via JIRA, it will be using a JIRA Workflow.
簡易ワークフローは次のメリットを提供します：
| 簡易ワークフロー | JIRA ワークフロー |
|---|---|
Has three default steps for Scrum boards: To Do, In Progress, Done. 4 つの カンバンボード用の既定手順：バックログ、開発選択、進行中、完了 | Has more steps than are typically needed on a board (e.g. see the default JIRA workflow). |
| 列間で課題を自由にドラッグできる | 課題がすべての列間で自由にドラッグされないようにするワークフロー "条件" がある。 |
トランジション時に画面を表示しない – すべてのトランジションは即座に実行される。 Automatically sets a resolution of 'Done' when issues are transitioned to the desired statuses (choose the desired statuses by ticking the checkbox next to the status when configuring the board's columns).
| Displays screens for Resolve Issue, Close Issue and Reopen Issue. |
| Can be edited from within GreenHopper (see Adding a new status on the Configuring Columns page), provided you have the 'Administer Projects' permission (for the one project that is on the board). | Can only be edited via JIRA (see Configuring Workflow), not from within GreenHopper. |
For details about steps, transitions and conditions, please see the JIRA documentation on Configuring Workflow.
簡易ワークフローへの切り替え
If your project(s) are currently using JIRA workflow, you may want to switch to Simplified Workflow. You will then be able to easily add new statuses from within GreenHopper.
簡易ワークフローに切り替える手順は、次のとおりです：
Before you begin, please back up your JIRA data (see the JIRA documentation on Backing Up Data). Please note that switching to Simplified Workflow will migrate all of the project's issues to the new workflow, which may take some time. (The project's original workflow and scheme not be changed, so any other projects using these will not be affected.)- Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
列タブをクリックします。
Click the Simplify workflow button as shown in Screenshot 1 (below).
In some cases this button may not be available — please see Why can't I switch to GreenHopper Simplified Workflow? (below).- プロジェクトはスクリーンショット 2 （下）に示すように、簡易ワークフロー使用に切り替わります。ステータス追加ボタンが表示されるようになります。
スクリーンショット 1 ：「ボードの設定」画面 （「列」タブ）－このボードは 簡易ワークフローを使用していません：
Screenshot 2: the 'Board Configuration' screen ('Columns' tab) — this board is using Simplified Workflow:
ボードが簡易ワークフローを使用しているか、どうすればわかりますか？
- Select Agile > Manage Boards from the top navigation bar, then click the Configure link corresponding to the board of interest.
列タブをクリックします。以下を確認すると、簡易ワークフローの使用状況がわかります：
The following words: Using Simplified Workflow (see Screenshot 2 above)
orThe Simplify workflow button (see Screenshot 1 above)
or- 次の表記： 簡易ワークフローは利用できません（以下の説明を参照してください）
簡易ワークフローに切り替えられないのはなぜですか？
以下のすべてを満たしている場合のみ、簡易ワークフローに切り替えることができます：
- 1 つのプロジェクトのみボードに表示されている（これを確かめるには、ボードのフィルターを見てください）
- That project uses a JIRA workflow scheme which only has one workflow for all issue types; and
- ワークフローは、アトラシアンによって提供されている事後操作、バリデーター、および 条件（いずれもアドオンでの提供なし）だけを使用している
- You have the 'JIRA Administrators' global permission; and
- JIRA バージョン 5 . 0 . 4以降を使用している（サポートされているプラットフォームを参照してください ）。
概要
コンテンツ ツール
アプリ
Log a request with our support team.
Raise an issue for our developers.
See answers from the community.
Tweet, blog and update our documentation.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.
49 Comments
Anonymous
Aug 14, 2012It looks like you have to actually have Administration access before you can click the button (ie, have attempted to do some other administration task and been challenged for your password again). Otherwise the process just fails with no clear explanation. It just says it was unable to convert the project.
Anonymous
Aug 21, 2012I had the same issue. Had to escalate my rights to perform administrative functions and then I could migrate the workflow. Thanks for the pointer.
Anonymous
Oct 23, 2012Thanks for the pointer, much appreciated. I went round in circles trying to find out why this wouldn't work. Going elsewhere to get full Admin access sorted it.
Rick Crow
Aug 15, 2012I do have JIRA administration authority, but I don't see the Simplified Workflow option for any of my projects that satisfy the criteria for being eligible for the simplified workflow option as stated on this page. I've even tried creating a test board from scratch from the Getting Started screen and created the board and project together ... and still don't have the option to use the Simplified Workflow.
Environment: JIRA 5.0.3 and GH 6.0.1
Rosie Jameson [Atlassian]
Aug 20, 2012Sorry for the inconvenience, Rick. The Simplified Workflow feature is only enabled for JIRA versions 5.0.4 and onwards, due to a bug in one of the libraries that JIRA uses. I have added this information to the page.
Andreas Grunewald
Aug 15, 2012So can I use the simplified Workflow across multiple projects once I have switched each individual project to the simplified Workflow in its own Rapid Board?
Rosie Jameson [Atlassian]
Aug 20, 2012Yes, you can have multiple projects that use Simplified Workflow, provided you are using a different board for each project.
Please note that each project that has been individually converted to a Simplified Workflow will have its own workflow (the workflows are not shared).
Andreas Grunewald
Aug 21, 2012But I would like to have 4 Projects in one board all projects using the same simplified workflow. Are you saying this isn't possible ? Not even once I have converted all projects to simplified in their own boards? How will a board work that combines multiple projects that each have a simplified workflow ?
Patrik Dibdiak
Aug 24, 2012I am wondering the same as Andreas. Rosie, the above explanations is implying that you cannot have multiple project in a single Board and still use the Simplified Workflow. Could you expand on it?
Rosie Jameson [Atlassian]
Aug 29, 2012Technically you can manually configure multiple projects to all use the same Simplfied Workflow. However, please note that in this case the "Add Status" button won't be available on the GreenHopper "Columns Configuration" tab.
Markus Krieg
Aug 29, 2012I can confirm that this works fine as long as you change the workflow of each of the underlying projects in the same way. There seems to be a bug, however: when you combine two projects created with the simple workflow, you see all the statuses of the default JIRA workflow instead. Once you drag the statuses from the columns to the Unmapped Statuses column on the left, they go away. Then you have to assign all the simplified statuses to the right columns.
Other than that, I like this new feature a lot! Many of our users have been wanting to customize their workflow to their needs, now they can do it. They can even combine projects with classic workflows with projects with simplified workflows as long as they take care in arranging columns and statuses. Most likely they should not assign a status that is only in one of the projects to the left or right-most column since they have special meaning.
Rosie Jameson [Atlassian]
Sept 03, 2012Thanks Markus, your first paragraph appears to relate to a bug – please see GHS-5639 - Getting issue details... STATUS .
Glad you like this new feature!
Anonymous
Jan 03, 2013Please explain how you did this. As they cannot share a common simple workflow I dont see how you can assign each a simple workflow
Markus Krieg
Aug 16, 2012There seems to be a bug that prevents seeing the Simplified Workflow option in JIRA 5.0.x although this version is advertised to work with Greenhopper 6. After updating JIRA to 5.1.x, I could see the option to switch workflows!
Rosie Jameson [Atlassian]
Aug 20, 2012Thank you, I have updated the page. The Simplified Workflow feature is only enabled for JIRA versions 5.0.4 and onwards, due to a bug in one of the libraries that JIRA uses.
rainer mueck
Aug 22, 2012Question: what is this feature good for? which problems does it mean to solve? I tried it out and currently I see that it only potentially creates problems ... can it be disabled completely on system level?
thanks in advance
Philip Page
May 07, 2013I think this feature is awesome. It allows you to have a simply workflow without having to map all those pesky arrows and transitions. All states can move to all states. That's how I like my boards. I had a workflow that allowed for that, but I had to create a bunch of transitions and if I wanted to modify my workflow it would be much more work.
Dave Geddes
Sept 07, 2012Does a project admin need global admin rights in order to use the new simplified workflow, create custom statuses, etc, or is it just the initial clicking of the "simplify workflow" button that requires global admin rights? Seems like it would make no sense to have to give every project lead global admin rights just so he can customize his workflow/statuses.
Rosie Jameson [Atlassian]
Sept 10, 2012You need the 'Administrators' global permission in order to convert to Simplified Workflow, but after that you only need the 'Administer Projects' project permission in order to add/delete statuses.
Andreas Grunewald
Sept 10, 2012I think the biggest issue I have at the moment with the Simplified workflow is that I can not resolve the issues so that JIRA sees the issue as resolved. Many of the other JIRA Dashboard graphs and filters expect a resolution for resolved issues. If the resolution is unresolved it doesn't matter what the status is. This needs to be fixed to make the Simplified workflow work with the rest in Jira. And having to modify the Workflow manually is out of queston because then it isn't simplified anymore.
Added a story for this in the Greenhopper backlog GHS-5902 - Getting issue details... STATUS
Markus Krieg
Sept 11, 2012This seems to work with the default "Done" transition when I start from the simplified workflow. However, on projects that I converted from the default JIRA workflow, this is no longer working because I kept the Closed status from the default workflow and deleted the Done status from the simplified workflow. Another side effect is that my closed issues can no longer be edited which is a great benefit of the simplified workflow compared to the default.
So I guess that we might need some additional logic that can be set for columns in the Board Config Columns dialog. This logic would be added on top of the workflow transition properties, post functions etc. Stuff like "set resolution to resolved" (post function) or "allow editing of closed issue" (property). To keep things simple for now, the last column could implicitly set the resolution because it is already considered the "green" status.
If you want to make this more complicated, you could consider something like a simplified workflow template for JIRA admins in the future. This should also include properties for statuses (columns) that the user cannot delete or change in order.
What do you think?
Andreas Grunewald
Sept 14, 2012Something like that needs to be done and it needs to be done fast. All our JIRA graphs are looking totally wrong because non of the issues have a resolution
Stuart Munton
Oct 09, 2012I had the same problem with the JIRA graphs not being updated after I had moved from a JIRA workflow run project to a GreenHopper simplified workflow run project.
The way I solved the issue was to create a new project using Greenhopper and then used the simplified workflow that this project created as the new workflow for the original project.
I was put me through a status mapping / transition screen and then JIRA did the mass update.
I then had to re-map the status on the rapid board configuration and then finally mass update my 'Done' status items back to 'Done' so that it set the resolution field to 'Done'.
Hope this helps.
tiongks
Sept 14, 2012This might be stupid question but what happens if we modify the generated simplified workflows, you know, the one that says "Do not manually modify this workflow."
We're using Atlassian OnDemand, does it get overridden during the next update/patch?
Mac Newbold
Nov 13, 2012I have the same question. We need to put some permission controls on the transitions in our workflow, but so far I'm not seeing a way to do it unless it's safe to ignore the "Do not manually modify this workflow" message...
Rosie Jameson [Atlassian]
Nov 18, 2012Waleed Anbar
Sept 27, 2012I'm using rapid board on a single project, however I'm not able to see bugs in plan or work modes. Our bug workflow has been customized, but the all the statuses are mapped via Rapid Board configuration. Our bugs have some custom statuses and transitions, e.g. Open status > Resolve transition > Ready For QA status > Verified in QA transition > Ready for staging status, etc.
Is it required that we use the simplified workflow in order for bugs to appear in plan/work mode? Will an issue type be excluded from display if its transitions do not conform to what Greenhopper knows how to manipulate?
Anonymous
Oct 05, 2012Is there a way to manually set resolutions? I want to be able to reject issues without ever moving them through a workflow.
There are issues being added to a backlog that are to be rejected even though they never move to the done category. I have no way right now to edit the resolution of issues. How is this done?
grt
Mark
Anonymous
Oct 10, 2012Why can't you have the simplified workflow for boards with multiple projects? It looks like a bug. When will this be fixed?
//Mikael
Why can't you have the simplified workflow for boards with multiple projects. It looks like a bug. When will this be fixed?
//Mikael
Mariana Santos
Nov 06, 2012I have Admin access, GreenHopper v6.0.4 and JIRA v5.0.4 but still I can't change to Simplified Workflow: GreenHopper Simplified Workflow unavailable.
What else do I need to check?
Anonymous
Dec 18, 2012Is there anyway to change the standard GreenHopper Simplified workflow for your JIRA Instance so that all subsequent projects created will use the new GH Simplified workflow???
Nicholas Muldoon [Atlassian]
Dec 18, 2012Hello,
This is not currently possible. Something similar is the request for board templates, you can view, vote and comment on GHS-6790 - Getting issue details... STATUS .
Thank you,
Nicholas Muldoon
@GreenHopperTeam
Jamie Echlin
Jan 14, 2013GH really needs to say why it cannot simplify a workflow. All the validation is already done and an errorcollection is created every time you go to the configure page, so I don't see why you cannot simply show the reasons a project workflow cannot be simplified.
The only way I have been able to get this information atm is by copy the production database and stepping through the source.
However, the error "gh.workflow.simple.workflow.potential.error.query.exactly.one.project" has at least 3 different reasons so needs to be broken down. The latest problem I see is that the workflow cannot be simplified if the workflow scheme as say N references but all to the same workflow, and no others. Yeah, it should never have been set up like that but it was.
Anonymous
Jan 22, 2013It would be great to be able to have resolutions mapped to the "Statuses" in the "Column"
Moving it to the Done column.
Done - resolution "Complete"
Done - resolution "Wont fix"
Wesley Monroe
Feb 25, 2013One thing our teams have relied on is having remaining work time set to zero (0) when the issue is closed. This helps with thing like keeping a semi-accurate hours burn down chart, even if the team doesn't explicitly log time. We could create a workflow post function to automatically change it to zero, but this feels like something that the default greenhopper simplified workflow should just do this by default. How about it Greehoppers? Thoughts/input?
Boris Berenberg
Feb 25, 2013Doesn't this kind of process hide any consistent mistakes which occur in estimation as burndown will always seem to be estimated correctly?
Anton Panferov
Mar 20, 2013I don't think so, because open issues are still open issues, so if your sprint slips (you're closing issues slower than you expected) you'll see it on a burndown chart. I believe the idea of burndown chart is not to show you how accurate your estimate for each issue is, but to show, are you still in time or not.
Boris Berenberg
Mar 20, 2013Hey Anton,
Consider the scenario where an issue was estimated to take 4 hours, but only took 2 hours. Then every time you close any overestimated issue, it is auto set to 0 remaining hours. The result of this is that your overestimation will be hidden into your burndown chart. You should then be tracking this delta across sprints to see if your estimation is accurate or not.
If you don't care about loosing overstimation information, then you are welcome to create a post function to clear the remaining time as Wesley suggested above. GreenHopper will not automatically do this for you.
Cheers,
Boris
Anton Panferov
Mar 20, 2013Just run into the same problem, did you find any solution?
Ian Bussieres
Mar 19, 2013JIRA OnDemand version : 6.0-OD-07.2
Administrative rights.
Even when I create a brand new project, using default JIRA workflow and create a Scrum GH Board for that project, I still cannot switch to simplified workflow. What am I missing ?
Rosie Jameson [Atlassian]
Mar 19, 2013I'm not sure what the issue could be here. Can you please contact http://support.atlassian.com ? Many thanks
JulioV
Mar 20, 2013Can we update the documentation? It seems that this statement for Greenhopper Simplified Workflow:
"Displays no screens on any transitions – all transitions will happen instantly. (Automatically sets a resolution of 'Done' when issues move into the 'Done' column.)"
...is not true in all cases (or is only true when left unconfigured) as seen in the Workaround instructions here: Unable to set issues to Resolved using Greenhopper Simplified Workflow
Boris Berenberg
Mar 20, 2013Thanks for suggesting this, I have made this change.
JulioV
Mar 20, 2013Wow, you guys are fast! Thanks!
Test Client
May 09, 2013I'm trying to set up a new kanban board with this 'simplified workflow'. I am currently using on project in JIRA that already has numerous scrum/kanban boards that are set up.
My question is will this affect any existing boards as well as screw up anything with the project? Or will this only affect the new board that I am setting up? I want to set this up with our JIRA administrator but want to make sure that I'm not going to adversely affect any already existing things. It is imperative that nothing changes and the other boards keep the same flow as before. I only want this one particular board to have the simplified workflow.
Thanks
Mac Newbold
May 10, 2013Workflows belong to a Project, and each issue has a workflow. So the issue will be subject to that workflow, regardless of the boards on which the issue is visible. You have to choose what workflow you want your issues to use, then the boards (all) automatically follow that workflow. They will never allow you to circumvent your workflow, or to have different workflows used on different boards for the same set of tasks.
Test Client
May 10, 2013Thanks. I just really want to get some sort of a more customizable kanban board for a particular thing that I am trying to work on. I want to add my own columns and change a few things around, which the default setup doesn't seem to let me do properly.
Test Client
May 10, 2013Thanks. I just really want to get some sort of a more customizable kanban board for a particular thing that I am trying to work on. I want to add my own columns and change a few things around, which the default setup doesn't seem to let me do properly.
Jean-David Dessaint
Jun 27, 2013Hi,
I've change a workflow into a simplified one in a brand new project and then added a new column. But I'm unable to add a new status: the Add Status stay gray. I'm Project Administrators of this specific project.
What am I doing wrong?
Just in case I change the owner of the project to myself. The modification has been saved but now I'm getting error messages at page refreshes and log in:
Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues.
Details
Environment
thanks