John Funk Community Champion

It depends on what you are trying to accomplish. Are the fields intended to be seen on one or two projects (or a handful) only? Are they only associated with certain Issue types? 

Hi Alex, First you should use an Issue Transitioned trigger not a field change for the status field. Then you wouldn't need that condition either. Make that change and see if it works for you. 

Great! Glad to hear. 

I would go ahead and report it to Atlassian support then. 

I would go ahead and contact support. 

Olá Gabriel, Você pode compartilhar a regra que você tem até agora?

Hi Laura, Sure - you can create an Automation rule with a Scheduled trigger. Leave it for running every one week. Then just to test, put in a JQL query on the trigger for Key = ABC-123 where that is the key for one of your issues to test. Then add a new action for Edit Issue. Select Due date, click the 3 dots to the side…

Hi @Plamen Todorov - I am marking Mark's response as Accepted. Let us know if you still need assistance with this one. 

You might try a multiline text field (Paragraph) and change the renderer to Wiki-style. Then see if you can apply the html code there. 

Hi Austin - Welcome to the Atlassian Community! Can you share some more information? Where are you looking for the issue? What is the message when the user clicks on the link but can't see it? Does the user have the Browse Project permission on the project for the link? 

Hi Siobhan, If you are creating the custom field as a URL custom field type, the value in the field must start with https:// and if it does, it should be hyperlinked. Can you share a screenshot? 

See Chella's response above. Not sure if that works for you or not. The only thing I could think of was to move everything up a level and use Initiatives like Epics and Epics like Internal Task 1 and Tasks for Client Task. But you would need a Premium Subscription to get Advanced Roadmaps. 

Hi Janez, I don't use ScriptRunner, but using Automation for Jira you would use: {{issue.description}} {{issue.field 1}} {{issue.field 2}} So for the Description field, the first part would keep the existing value of the field and then the next two would be whatever the actual field names are of the other fields. Not sure…

Taking the bus multiple times on the Yungas Road when we lived in Bolivia. It's also known as the World's Most Dangerous Road or the Death Road locally there. 

Hi Harish, Can you be more specific? What is it that you are wanting filled in? If these are ongoing clients you could enter them into the Assets module (would require a Premium subscription) and retrieve data about them from there. Other than that, this information is not stored in Jira. 

Ah, yes if it is in a Sprint, it will follow that. 

Hi @Erwin Veldhuizen - Did you ever get Insight to work with your Team-managed project? 

Do you still need to be an Admin on those projects? If not, drop yourself from that role. 

Hi Brian - Welcome to the Atlassian Community! Create a rule based on a Field Value Changed trigger. Enter any conditions that you want. Add a Branch for Linked Issues Then under the branch add an action for Edit Issue and select the Due Date field. In the due date field use the code: {{triggerIssue.duedate}}

Hi Bryan, Make yourself the owner of the rule. You can change the parameter to email you went the rule fails once or every time it fails. 

Hi Prabuddha - Welcome to the Atlassian Community! Just some clarification - only Agents will see that field. The thought is that someone might call the help desk or send and email and the Agent will enter the request on the behalf of the user. Users coming directly to the Portal will not see that field in the form and…

Thanks for the article. And great meme- I used to work with Rachel Cruze!!

You are very welcome.

Hi Elise - Welcome to the Atlassian Community! If you click on the Search box in the top navigation bar, you can enter some information such as a name or part of the key of the issue. Or when you click in the Search box you can then click on the Advanced Issue Search link in the bottom of that pop-up. Then you can provide…

Hi Raghavendra - Welcome to the Atlassian Community! What date are you wanting to use? And also the other information? If you are wanting to fill in the name of the user and their email and the today's date, that's not necessary - that will be populated when the issue is saved.

Hi Sonal, Please note that transitioning the parent and adding text to a field are two different steps. Have you created the rule yet and just need help? If so please post the rule here. If not, create the rule and we can go from there.

Hi Sharla - welcome to the Atlassian Community! Those issue types are Standard issue types which are the first thing you are looking for. You probably just need to take out the parts about standard and sub-task types.

I would discourage deleting issues. They can be closed out, but I don't think it is a good idea to delete them. 

Hi Jon, If these are both Company-managed project types, then you will few if any problems. The existing schemes can also be used with the new project. You will need to manually configure your Project Roles in the project, and you should add any existing Components and Releases to the new project (use the exact same names…

Hi Alixanne, Sure you should be able to do that. Create a trigger that will Clone or Copy the Issue. Then add a step (i.e. component) to the rule Link the two projects. So, after you do the action to Clone or Create a new issue, the add a Branch for Most Recently Created Issue. Under the branch add an action for Link…