John Funk Community Champion

Yes, it looks like you will need something like Automation For Jira or another add-on. 

Hi VA, Issue Level Security is not currently avilable for Next-gen projects. You can follow and vote for the Feature Request here: https://jira.atlassian.com/browse/JSWCLOUD-18843

I still think it is a permission issue somewhere. Take a look at the Permission Scheme for that Project to see who has Transition Issue permissions. The atlassian-addons-project-role needs to be there. 

Hi @Care Knot - Welcome to the Atlassian Community! You should also open a ticket with Atlassian Support. They more they hear, the more likely they are to do something. https://support.atlassian.com/contact/#/

Did no one from Atlassian respond?

Hi Patrick - Welcome to the Atlassian Community! One option might be to create a "dummy" user (or two to save you time). Grant one user access to Projects A1 and A2 and the other user Project B. You will need different email addresses but you should be able to create some gmail accounts for that. You can make the users…

Hi Tim, There are some issues around Epics and linking them in Automation For Jira currently. You can follow along here with the development: https://codebarrel.atlassian.net/browse/AUT-1641

Okay, cool - thanks for sharing! First, it's overkill to have all of those groups in the Manually triggered as all users who could do anything are in the jira-users group. So you if just used that group it would catch everyone, which also begs the question, why even limit it? But that's just a side issue. ;-) So that…

I would start by looking at the permission scheme for the target project. Be sure that the Browse Projects and Create Issue permissions are available to the atlassian-addons-project-access Project Role.

Hi @CHEUNG Crystal - Welcome to the Atlassian Community! I just tried it with one of my existing filters and custom single user picker field and it worked fine. Is you user picker field a single pick or multi pick?

Hi @Дятченко Александр - Welcome to the Atlassian Community! See if this previous post helps you: https://community.atlassian.com/t5/Jira-Questions/custom-field-for-new-JIRA-next-gen-project-does-not-show-on-form/qaq-p/1167332 There is also more information here:…

Hello and Welcome @Hye-Jin Kim ! We are glad you are here!!

Thank you for your answer - I am sure I will have more questions around the actual execution. My question about Jira to AD was not so much about using Access to do that but is it even possible - maybe using webhooks or the API as such.

Thanks for taking the time to do this! I do not have direct functions in this area so I am not sure of all of the technical workings. But I am the Jira administrator and would love to make this work with automation. This might be a little too specific and/or too involved with answer here, but I will give it a shot. :-) We…

Hi Jeremy, I don't use the Server version so I don't know if it looks the same or not. But in Cloud when I go to Settings > Issues > Screens in the list of "View Screens" there is a column for Workflows which shows which workflows the screen is used in. Hopefully there is something similar in the Server version. 

That would be an internal company thing. Do you have some way in your company in which to ask that? Maybe previous emails from someone within the company?

I forgot it was a Next-gen project - thanks for that reminder. No, those project types don't have a permission scheme. I would back out your new custom roles one by one until it works again to see what was the culprit. 

Hi Paulo - Welcome to the Atlassian Community! You will need to have Site Administrator privileges, but go to Settings > User Management and add the user there. You will need to invite them. I would then create a new group called External Users or something like that and add them to the new group. Then you can control…

Hi Kimberly - Welcome to the Atlassian Community! From your description of the situation, I am assuming that this is a Classic Software project with a shared workflow scheme. If that is indeed the case, then you will need to contact a Jira Systems Administrator for your company to make the change for you. 

Hi Romel, First, it is better to create a new question for each new situation. But for now, please check the permissions in the Permission scheme to make sure that the atlassian-addons group pretty much has all of the permissions. 

Hmm, that description is very misleading then as it says it will append the value. "If set, the given value will be appended to the field."

Hi Olaf - Welcome to the Atlassian Community! Have you started to build the rule yet? If so, can you share what you have so far and what you need assistance with? If not, see this basic information to help you get started: There are two types of automation: * Global: In the Free version, you get 100 executions per product,…

Hey Bill - do you know if Automation For Jira will actually create the version if a value is added to an empty field? That's what he is trying to do. 

Let me see if someone with Atlassian can help you. 

Can you share a screenshot of the rule? And just to verify - you are a Jira Systems Administrator?

Hi Daniel - Welcome to the Atlassian Community! I don't know what it is not appending the value and is instead replacing the value. You might want to create a support ticket for Atlassian to investigate. Another option is to create an Automation For Jira rule and try to append it that way. 

Maybe check the Link Issues permissions for the RTO project to see who can actually do linkages. 

Thanks - that's helpful! So the issue is that the layout for the new issue view only allows multi-line fields in the center section and pretty much all other fields are on the right hand side. That is not something you can change. You can reorder how the fields show up from top to bottom but that's about it. You can follow…

Ah, it sounds like you are using the built in Automation tool and not specifically Automation for Jira. Can you confirm that? Did you follow this path: You'll need to be a Jira Admin/Site Admin, go to Jira Settings > System > Automation Rules (left-hand menu)?

So you might try the Automation For Jira Lite free add-on. Otherwise, you will probably need to open a support ticket with Atlassian to see why the field is not showing up. https://support.atlassian.com/contact/#/