John Funk Community Champion

Yes, you can do that in the same way you did it when both were Jira Software projects. It will work the same way. You just need to have the appropriate permissions in each project. 

Hi NZ - Welcome to the Atlassian Community! If all of the issue types are present in the target project issue type scheme as the source project, then the hierarchy should be maintained. 

Hi Cheng, Is the custom field a text field? If so, then yes you can can use the ~ (tilde) to query it. For example: "Software Component" ~ AKS

Hi Bernard, I assume you are using a Team-managed project. Can you verify that? If so, I an not sure you can change that. I have not found a way either. I would suggest to either use a Company-managed project or create a second board that you could use with your Team-managed project. 

Is your rule based on Field Value Changed (Risk Score)? If so, then it should work as Kalyan has described. Can you share your rule? 

Hi @jira-sales Sure, you can do this by creating an Automation rule. If you will explain your use case in more detail, we can give you a more detailed answer.

You are welcome.

Hi @Jeen Jeong - Welcome to the Atlassian Community! Please create a new question so that more people can see it and respond AND can provide better answers to your particular need. 

UPDATE: For those just now finding this thread or have posted already, here is an update for a workaround. This could be solved simply enough by putting in a Default value. HOWEVER, default values are at the field level so ALL issues using the Description field would have that same default value. Obviously, that is not the…

It sounds like you want to do this because the user doesn’t know the Epic name and would have a hard time finding it. If that’s the case then you are probably better off using Components and making the field mandatory. Then you could create an automation rule that populates the Epic based on the Component when the issue is…

Hi Gabriel - Welcome to the Atlassian Community! You can create a filter and the export the results. Click in the Search box in the top nav bar on the upper right. Choose view all issues. Enter your query and click the search icon to see the results. The add and take away whatever columns you like. Go ahead and Save the…

Take a look at this article and see if that helps. https://support.atlassian.com/jira-cloud-administration/docs/allow-anonymous-access-to-projects/

Sure - you can use it in your office, you would just connect through the browser.

Hi Shivagari - Welcome to the Atlassian Community! How is it that you’re wanting to combine them? You can have issues on both and connect them to link issues. Or you can create an additional board that combines issues from both. Or you can simply move all of the issues from project management one into Jira management into…

Hi Inoke - Welcome to the Atlassian Community! What type of project is this? Team managed? Company managed? Jira Software? Jira business? And you said dashboard, but do you really just mean board ?

Hi Rona - Welcome to the Atlassian Community! Yes, you can link them together through connecting issues. It’s not a bundle per se, but you can use them in conjunction with each other. What is your exact used case or scenario?

Hi Ivander, It depends on how your workflow is set up. But you can modify or customize your workflow to go forward and backward if you like.

Hi Ivander - Welcome to the Atlassian Community! No, it considers that an advanced function.

Hi Ayden - Welcome to the Atlassian Community! No, that is not possible. 

Hi Farhan, Jira Work Management is a Cloud only application. 

Hi Mathew - Welcome to the Atlassian Community! There are some challenges with the cloud-to-cloud migration tool Atlassian provides, but all-in-all I would say it is less painful that server migrations. Assuming you don't have a lot of add-ons that also need to be considered. But there's considerable clean up to happen…

You are welcome. 

Happy to help!

Create an automation rule based on a Scheduled trigger. Have it run once a day - maybe early in the morning 3 am or 4 am or 5 am or something like that. Add a JQL for the trigger that looks like: project = ABC and "Due Date" = startOfDay() Click the verify to make sure it shows at least a valid issue for testing purposes.…

Hi Muhammad, The way we solved it in the past was to find some way to group several of the top level options. Then create either a custom field for groups for those fields or use say the Components field and add Components for each group. Then create multiple Cascading custom fields - one for each group. So that looks like…

That's controlled under Settings > System > Global permissions. See the section for Share dashboards and filters. The Org Admins group is probably listed there.

Hi Samba - Welcome to the Atlassian Community! No, that is not possible with out of the box Jira. 

Hi Jessica, Have you added Feature as an issue type to your issue type scheme for that project? Have you added the Parent field to the screen? If you have done all of that, is there nothing showing in the Parent field on the Epic? Or just not what you want? 

Hi Mike - Welcome to the Atlassian Community! What is the field that you are using to currently capture the name of the new hire? And yes, you can go ahead and create the two fields for "First Name" and "Last Name". In fact, I am going to assume you already have for the the rest of this. But one more note, you need to…

Hi Suzy, You don't need the Additional fields/advanced section. Click on the 3 dots next to the Summary field and choose Set to. Then put this in the blank box: Seat Request {{issue.customfield_10116}}: {{issue.customfield_10243}} - {{issue.reporter.displayName}} - {{issue.customfield_10078}}