John Funk Community Champion

Hi Katerina - Welcome to the Atlassian Community! You can create an automation rule to do that. You can either have a manual rule that you execute from the initial ticket, or you could have the rule fire automatically when the first ticket is created. Since I don't know when you want it to be executed, I will go with a…

Hi Chris, Built-in approvals only show for Jira Service Management projects or Jira Work Management Team-manage projects. 

The Condition is on the transition in the workflow. Edit the workflow, click on the line for the transition, and see if there are any Conditions there. 

Hi Joey, Can you share the notice you received?

else if writer = Jack then assignee = Jack Awesome That line will fail every time. Just saying

You need to create separate screens for Edit and View. Then leave it on the View screen and remove it from the Edit screen. 

Hi Svetlin, If you remove the field from the Create Screen and make the field Optional in the Field Configuration, that should be enough to accomplish what you want. The only way to remove the field from the field configuration would be edit the Context of the field and include only certain issue types. Then create a Field…

Hi Cathy, You can go about this a couple of ways. One is to simply book mark the boards in your browser. That's what I tend to do. Another option is to rename the boards to start with a number or the letter A because the boards are listed alphabetically. Other than that, you will not be able to change the order in which…

Since it is Team-managed project, you will need to create the Custom Fields in the shared configuration for Company-managed projects. Go to Settings > Issues > Custom fields. But search for the field first to make sure it is not already there. 

Hi Martin, No you will not be able to modify the interface in this section of the screen. 

@Kristján Geir Mathiesen - even a blind squirrel finds an acorn every now and then. hahaha.

Yeah, if you can populate another field with a user value (the customer would NOT be able to do that), then you should be able to copy the user into the Approvers fields. 

You might could do it as Jack suggested with a text field. You could certainly invest a little time to try it out. But you should put the email address of the user in the text field because that's really what Jira connects to for users. Then we can see if we can copy that value into the Assignee field. 

How we doing @Katie Dodson ? Did you get to try it out?

Hi Yena, You can do manual backups of a single project with they Revyz Data Manager for Jira. https://marketplace.atlassian.com/apps/1228694/revyz-data-manager-for-jira-backup-restore-analyze-optimize?hosting=cloud&tab=overview Full transparency, I am an advisor for the app. 

Yes, change the name of one of them. Just add a dot or 2 or something like that after the name. 

Leave it as Org Admin, just add yourself as a Customer on the JSM project in the Project Role. Or have the project admin do it. 

Hi Shaun, Unfortunately, there is no way to change the field type. You will need to create a new field with the next type. Although Jira will let you name the field the same exact name, you shouldn't. You can update it to the same name as the current one eventually (after fully deleting the current one). After you create…

Hi Rim, Your syntax is wrong there. Why don't you just use Audience? There is no need to do custom field there, nor do I think it will work in JQL. 

Hi Katie - Welcome to the Atlassian Community! No, the Org Admin does not have to be an Agent in JSM. They can just be customers. 

By the way, Jack is old and senile. But feel free to trust him if you want.

Yes, the Company-managed ones are there - but just sort of hidden for some reason. If you are using Jira Software (vs. Jira Work Management), then click on Projects, Create Project. Then click on Software Development on the left. Then Click Kanban. Then click Use Template. You should be able to select Company Managed…

Nope, not for Sprints. It has to be in far right column.

Hi Santhosh - sorry but I am I not user of Jira Product Discovery, so not sure how the calculations happen. 

Hi Gustavo - Welcome to the Atlassian Community! Make sure all issues are in the far right column of the board. Only issues in this column of the board will be considered completed, regardless of the status. 

Hey Jack - not sure if there is a JAC ticket or not. This is where I found it: https://support.atlassian.com/cloud-automation/docs/limitations-in-team-managed-projects-for-automation-rules/

Hi Vamsi, You can implement Issue Level Security for that. https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Mine are all pretty much baseball caps - though I don't wear anything much any more. And more than one of the caps if from Atlassian. :-)

Unfortunately, in doing some more research I have found this: * Custom fields: All People custom fields in team-managed projects currently aren’t supported by Jira Cloud automation. This means that your automation rules won’t be able to access values or set values in any People fields. That's why you are not seeing the…

OK, I’m going with the proverbial it depends. To be honest, with my clients, they’re mostly focused on one product anyway. So I would probably go all out on that one. My biggest hesitation on that and being the free subscriptions on everything else is simply the lack of security and being able to control permissions. But…