jira.issue.editable property seems not to work

[Anastasia Kozlova]

Hi folks,

I am putting a property to my workflow transition, but an issue still remains editable.

I tried those ones:

• jira.permission.edit=denied
• jiia.issue.editable=false

When I'm exporting a workflow as an xml file, I can see the following:

<action id="61" name="My transition">
 <meta name="jira.description"></meta>
 <meta name="jira.permission.edit">denied</meta>
 <meta name="jira.fieldscreen.id"></meta>

or

<action id="61" name="My transition">
<meta name="jira.description"></meta>
<meta name="jira.fieldscreen.id"></meta>
<meta name="jiia.issue.editable">false</meta>

Any ideas?

[Deleted user · Accepted solution]

According to https://answers.atlassian.com/questions/6569/how-do-you-burndown-story-points-in-greenhopper-on-a-daily-basis ...

"GreenHopper does support burning points. When you complete the story the points will be burned. As Tommy points out the right hand side column is your definition of done, so once a story is done it will be burned."

since the defination of done is fixed the requirement is not achievable...

[Martin Aparicio]

You can try setting a resolution for the Testing status. But I don't think you will be able to have two burndown charts.

[Deleted user]

Resolution is set in the 'Resolved' stage per the default jira workflow, which is prior to the addition of the 'testing' stage, unforuately this does not seem to be the criteria by which the rapid board burn down chart 'burns' down a task.