greenhopper action denied "Your JIRA workflow forbids this move."

I am evaluating greenhopper.

On SOME issues when trying to move from In Progress to Done I get this message "Your JIRA workflow forbids this move." But not for all issues.

I also get this error when trying to reopen SOME issues by dragging from "done" to "to do"

I looked at the other posts on this topic and I believe that I have implemented all the other suggestions.
1. All statuses are assigned a column ( default setup ) in "configuration board"
2. Auto Assign is set ( ALL ISSUES I am dealing with belong to me anyway )
3. default jira workflow so no conditions to meet.

Any other ideas?

Hi edr,

Actually if you are using the JIRA default workflow you do have 1 condition.
The issues need to be assigned to the user before he can strat progress on it.
That is a condition I think.

So you have 3 solutions here:
1) Withdraw that condition from your workflow
2) Assign the issue to you before doing the drag
3) Set the Auto-Assign setting in your Project > GreenHopper > Configuration > TASK BOARD MAPPING or directly from your TaskBoard user prefereneces.

A good way to see if you do have right to do the move is to actually look in the JIRA Issue standard view and check the "Workflow Actions" that are available. In this case I can asure you that you wont see the Start Progress action if the issue is not assigned to you first.

Let me know how it goes.

Cheers,
JC

Unfortunately the bbs seems broken as the quote strings show up in the preview ....

But not in the submitted post :(

jchuet wrote:

Hi edr,

Actually if you are using the JIRA default workflow you do have 1 condition.
The issues need to be assigned to the user before he can strat progress on it.
That is a condition I think.

As per my original post all the issues belong to me, so this condition should not be a problem????

So you have 3 solutions here:
1) Withdraw that condition from your workflow

Since all these issues belong to me I should ignore #1?

2) Assign the issue to you before doing the drag

3) Set the Auto-Assign setting in your Project > GreenHopper > Configuration > TASK BOARD MAPPING or directly from your TaskBoard user prefereneces.

As per my original post, auto assign is set.

A good way to see if you do have right to do the move is to actually look in the JIRA Issue standard view and check the "Workflow Actions" that are available. In this case I can asure you that you wont see the Start Progress action if the issue is not assigned to you first.

So if we can assume the following:
1 that the item is assigned to me
2. In the task board configuration all statuses ARE assigned a column

What else could be wrong.

Let me know how it goes.

Cheers,
JC

[b]

If you take an issue that you cannot drag into the in progress column and look at the issue in the JIRA standard view. What are the "workflow Actions" available?

Cheers,

jchuet wrote:

If you take an issue that you cannot drag into the in progress column and look at the issue in the JIRA standard view. What are the "workflow Actions" available?

Cheers,

In the greenhopperized jira on a test machine none.

In my real jira installation close and reopen ( for full disclosure greenhopperized installation is also an upgrade from real installation )

on green hopper it was dragged from done to "to do" to "in progress" as though it were reopened

HUmm... something is wrong with your Porject's workflow.
Are you sure you are using the default JIRA workflow?

This is not really a GreenHopper issue but more a JIRA configuation problem.

If you do not see the Workflow actions properly in your JIRA standard issue views that can only mean you have a workflow setting problem.

Now do remember that depending on your Issue status you will have access to only certain actions.
The issue that you have describe in your real env seems to be resolved thus there is no step to go back to the In progress state.

The JIRA workflow is as follow:
From Open you can go to In Progress, Resolved, Close
From In Progress You can go to Open, Resolved, Close
From Resolved you can go to Open, Close (NOT In Progress)
From Close you can only go to Reopen

Cheers,
JC

jchuet wrote:

HUmm... something is wrong with your Porject's workflow.
Are you sure you are using the default JIRA workflow?

This is not really a GreenHopper issue but more a JIRA configuation problem.

If you do not see the Workflow actions properly in your JIRA standard issue views that can only mean you have a workflow setting problem.

Now do remember that depending on your Issue status you will have access to only certain actions.
The issue that you have describe in your real env seems to be resolved thus there is no step to go back to the In progress state.

The JIRA workflow is as follow:
From Open you can go to In Progress, Resolved, Close
From In Progress You can go to Open, Resolved, Close
From Resolved you can go to Open, Close (NOT In Progress)
From Close you can only go to Reopen

Cheers,
JC

So the move in greenhopper was from done/resolved to "to do"

so if it were possible to upload a bmp or jpg I would put up screenshots of the apropos workflow screens ....

I is possible, you should have the Attach files button next to your submit.

Cheers,

Else send them to me at jchuet [at] atlassian [dot] com

This may be the problem:

mysql> select * from OS_WFENTRY where ID=( select workflow_id from jiraissue where pkey='<issue id>');
+-------+------+-------------+-------+
| ID | NAME | INITIALIZED | STATE |
+-------+------+-------------+-------+
| 15087 | jira | NULL | 1 |
+-------+------+-------------+-------+
1 row in set (0.05 sec)

mysql> select * from OS_CURRENTSTEP where ENTRY_ID=(select workflow_id from jiraissue where pkey='<issue id>');
Empty set (0.00 sec)

I am guessing an empty set for this last one is not good. How this issue got this way ???? It looks like issues with this problem have this entry empty

And BTW no attach/upload etc type button available to me ( but I think this new dataum removes the need for an upload of snapshots )

Try a consistancy checker from your JIRA > Administration > Systems

Cheers,

The Attached file should be when Posting a reply not doing a Quick reply no?

Cheers,

No attach file using reply at bottom of thread

edr wrote:

No attach file using reply at bottom of thread

no attach file type thing when I quote ....

Ok, what I have now done, the before mentioned empty set is not empty in my "real installation" so I have restored from xml backup ( old one was a couple weeks old anyway )

now I need to hunt down the jira trial and greenhopper licenses again...