Hi Jo,
you can prevent users from planning on closed issues by adding the jira.issue.editable Property key to teh Workflow step "Closed". Please take a look at the JIRA documentation https://confluence.atlassian.com/display/JIRA/Working+in+text+mode#Workingintextmode-uneditable_stepsPreventingissuesfrombeingedited for more information on how this is done.
Kind regards,
Susanne
Hi @Susanne Götz _Tempo_ , I just tried this on Cloud because I have the same request, but I'm still able to add a Plan for a closed issue with following workflow step properties:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Dave Mathijs
A lot of time has gone by since this question was asked, and my earlier response refers to the Server version of JIRA and Tempo (the provided link is for JIRA 7.3).
Since early 2017, JIRA and Tempo data for Cloud instances are stored in separate databases. JIRA has no information about plans that are created in Tempo and therefore planning on issues can not be restricted via a JIRA workflow.
Also, on Server/DC, a lot of changes have happened in the Tempo product line. The option to restrict planning via a workflow property is no longer available.
In the current version of Tempo, users can always plan time for themselves.
When only Tempo Timesheets is used, these plans are only visible to the user but not to anyone else (not the team lead, team members, or approvers).
When Tempo Planner is used, these plans are visible to team leads, and users who have the "View plans" permission for teams the user is a member of.
Can you please create a feature request for this in our Tempo Ideas portal, https://ideas.tempo.io/ideas.
Best regards,
Susanne
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your prompt feedback Susanne, I will add the suggestion.
We have a business requirement for one of our clients to disable planning on certain issues within a project. I'll try issue security as a temporary workaround.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
T-I-2228 has been created for this feature request on Cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.