John Funk Community Champion

It’s like any other software, you have to pay for full features. You can’t expect a free piece of software to do everything you want it to do. You can make the user an active and they will not have access to the project.

Hi Guru, Remove the field from the Edit screen and the user will not be able to change the value.

Hi Ryan, You can't just remove the linkage - you have to either convert the sub-task to the next level up (Story, Task, etc.) or link it to a different parent. 

Great!

Hi Sandra, It looks like you can with Advanced Roadmaps - but not sure with the standard roadmap. 

Hi Celeste - Welcome to the Atlassian Community! See my answer in this post: https://community.atlassian.com/t5/Jira-Software-questions/Permission-Scheme-for-project/qaq-p/2308079

Hi @Ivan Andrieiev - No directly - you would need an add-on like ScriptRunner Behaviours. You could remove the Assignee from the Edit screen and force them through a transition screen to add the Description field. But you need to do that on every transition and might be very klunky. 

How are you linking to the Configuration Items? Are you planning on using the Assets tool inside JSM? If so, then yes. See Dirk's note above. 

Okay, that's weird. Is the Planned Start Date field on the Create screen for the Story issue type? If so, the other thing to try would be to switch out the field name for the ID. So like this: {{issue.parent.customfield_18951.plusBusinessDays(8)}} Where 18951 is the ID for the Planned Start Date field. Go to Settings >…

Great! You are very welcome. Sorry for not being more clear to begin with. 

So the project manager is in an Epic, then clicks on the execution of a manual automation rule, and it creates the children stories identified in the rule (regardless of the project). Is that correct? If so, what I showed you above is what you should do for the Epic Link field in the children getting created. 

So what is the value for that field in the Epic (RDCELSA-260) now? And what is the value for that field in the Story (RDCELSA-269) now? 

So, can you lay out your scenario? What issue are you on when you do the manual execution? And what do you expect to happen? 

What issue types did you link the new workflow to when you added it to the workflow scheme? It says there are no issue types linked to it. 

Hi Jeremy - can you be more specific? 

Can you share some screenshots of what happens? 

What exactly did you try? And what exactly happened? Did the rule fire and didn't update the field? Did the rule fire and didn't meet the conditions? Check your audit log and post there here please. 

Can you share a screenshot of what it looks like when you click on Kanban Board while you are in the project? 

Yes, you can create hierarchies like that - but only in a Premium subscription plan. 

Hi Sanda, It should be as simple as adding a Condition to your workflow for the transition from Obsolete status to Done status and select the Only Reporter Condition. 

Hi Colin - Welcome to the Atlassian Community! What type of project did you create? Jira Software? Jira Service Management? 

Hi Felix - Welcome to the Atlassian Community! Try using this for the Planned Start Date field in the Edit Issue: {{issue.parent.Planned Start Date.plusBusinessDays(8)}} It's case sensitive so be sure the field name is exactly the same. 

Hi @Бондарев Руслан - Welcome to the Atlassian Community! Here is an article that will give you more information: https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-types/ Basically, issue types allow you to have different workflows on a project based on different types of work - e.g. Epics vs.…

Some great additions!

Hi Peter - Welcome to the Atlassian Community! Can you provide some more details? Maybe a screenshot of your workflow - especially showing the approval details in the workflow. Also, what platform are you on? Cloud? DC? Server? Finally, how are you populating the Approvers field with values? 

Hi @Autobrains Jira Admin - Did you ever get this solved? 

Hi Lottiah, This can be a bit messy, especially if you have not set up groups and permission schemes in mind for outside access. Basically, you want to create a Group in User Management for users from the outside. This can be a single group, but will mean that people from multiple outside clients have access to all of the…

Great!

Hi Guru, Where is it that you want to display this information? What are the steps you are doing and when do you want to populate this custom field? And why do you want a separate field and not just show the Key? The Key will not be generated until you create the issue. Then you can have an automation rule that copies the…

I have wondered that myself - but I have no idea why it's not there.