Mikael Sandberg Community Champion

Just to add to @Tomislav Tobijas excellent answer, you could use forms to display additional fields via the portal, no additional apps from the Marketplace needed. I wrote about it in this article, Using Forms to display additional fields in the Portal. 

Unless you either use the archive or delete of the pages that you want to hide they will continue to show up in searches as long as the user have access to the pages. How have you "locked" the pages?

Check out this article I wrote regarding passing data from one automation to another, Using smart values of incoming webhook with Jira Automation. By using the main automation as a dispatcher you can control when your sub automations are called, and if you need to turn one of then just disable the sub automation.

Hi @Suzi D'Apice-Chen, Welcome to Atlassian Community! You can do this by having multiple automations, maybe one for each team which are then called from the main automation depending on the conditions you outlined above. At my previous work I create our onboarding/off-boarding automations that way. My main automation was…

Hi @Ramirez, Crystal N., Welcome to Atlassian Community! You probably ended up here because your company is using an Atlassian product, From what I understand REDCap survey app and not related to Atlassian so you would probably get a better answer if you contact your REDCap admin. 

What you see is expected, IF conditions are evaluated sequentially the way your rule is currently configured. Currently For each branches don't have access to IF/ELSE conditions, you you would need to reconfigure your automation. One way would be to call a second automation that does the actual work and use the IF/ELSE…

Hi @Mikayel Bartikyan, Welcome to Atlassian Community! You would want to contact Github support for this. This forum is for Atlassian apps, and you probably ended up here because Github uses one of Atlassian's apps.

No, the token that you create in Assets can currently not be linked to an account, and no, you cannot set the username/password for it. The token is only tied to the specified import and cannot be used anywhere else, the permissions are limited to only be able to create/update asset objects.

This can be done with automation and Assets if you have access to it, or without assets if you are on the standard plan. If you do not have assets then the routing can be handled by using a lookup table that has the information regarding which team the app request should be routed to. If you have assets then that…

Hi @Liu, Ray, Welcome to Atlassian Community! Based on your description I assume you created the token from within Assets, correct? If that is the case then what you are seeing is correct. The token created in assets is not linked to an account (even if you are the one that created the token) and that is why it shows up as…

Hi @christina.miller Welcome to Atlassian Community! If you are on a standard plan or higher you can go to https://support.atlassian.com/contact/ to contact support.

AI Champion!

Hi @Anthony Bautista, Welcome to Atlassian Community! Please reach out to abuse@atlassian.com and that team will investigate. Please note that they will not reach out to you, but they will take action on it. 

You are charged based on the number of agents that you have, not the number of projects. You can learn more about the licensing if you go here and check out the FAQ at the bottom.

Because you are using bulk move the relationship will be lost. I would try creating the new "epic" and add it above the current one, then rename the original one to feature. This should keep the relationship since you are only changing the names of the work item type.

Hi @David Twomey, Welcome to Atlassian Community! On the customer sharing settings, change the setting so that customers can manually enter email address. This will create a new customer if they are not one already. The way you currently have it set in the project the customer would have to be invited first before they can…

Hi @Chopra, Melanie (Senior Forms Analyst - Forms Design - Brands Marketing and Experience), Welcome to Atlassian Community! My guess is that this is intended for your Jira team, not for the Atlassian Community! I would suggest that you contact your IT Helpdesk if you do not know who your Jira admin(s) are. 

Hi @Sreeja Pathapelly, Welcome to Atlassian Community! This is expected, epic link is the old field that parent link is replacing, and you can read more about it in this KB. 

That is expected, the value added in combination with create will never happen, since the work item hasn't been created yet. If you change the value added to any changes to the field value it should trigger. But I would use the Work item created instead as the trigger, and then use a condition to check the field value.

Like @Christopher Yen I used specific work items for onboarding and off-boarding. We started off by adding sub-tasks for external teams, but then changed it so we created tasks in each team's project, that way we didn't have to add/remove external users in the HR project. And I know one team used checklists as well, so…

Hi @Janelle Schultz, Welcome to Atlassian Community! The change was announced in this article.

That Copilot answer is incorrect. As you can see from this screenshot, Epic is grayed out and cannot be removed from the Epic level: Jira does allow you to rename work items, but if you look at the epic it is noted that you should not edit or delete that work item:

What does the audit log say? When you say it doesn't work, are you meaning it doesn't get passed the condition? Or is it the delete action that doesn't work?

First off, you cannot change the where epic is in the hierarchy, it will always be on the level one. If you move feature to not be above epic it will be on the same level as task/story/bug. And any changes to the hierarchy settings will affect all Jira projects, you cannot do it for individual projects. Regarding adding…

Hi @Erica Johnson Welcome to Atlassian Community! Since you are on DC, in the contact form make sure you select Data Center under "or select an app" on the right and then the app, that will bring up the page where you enter your SEN instead of the Cloud instance.

I have experience from using approvals both in JSM and Jira. In Jira I created my own automation since it didn't have the build-in feature until now, and I wrote about it in this article. I can see how this is useful, not just in the scenario I wrote about for recruiting, but also for software teams that need to implement…

The default work items in Jira are Epic, Story, Task, Bug, and Sub-task for Jira projects and their availability depends on the template you use to create the project. Feature is not a default work item, but since you are on the premium plan by default any new item types you create will be under Epic, but you can change…

The new conditions that you can add to the trigger may sometimes not work correctly due to a racetrack issue that Atlassian is working on. What you can try is to add the condition as its own component after the trigger and see if that works.

I would say that is a Chrome issue, not Confluence. My screenshot is from a Mac using Chrome 140.0.7339.133.

And you should still see the browser menu if you highlight the text and right-click.