Mikael Sandberg Community Champion

Have you tried to convert it to a JSON string using the asJsonString function? 

Hi @Maria Nicole Pugliese, Welcome to Atlassian Community! The short answer is no, you cannot have an issue show up multiple times on a board. The only workaround would be to create clones of the issues that have multiple components and make is so they only have a single component. 

Forms currently only have two permission levels, external and internal, which controls the visibility on the portal. You cannot set it so a specific form can be filled out by specific users. I have a similar project where privacy has their own form that the fill out. The form is added to the request after it is created,…

The numbering is based on the default behavior in Jira, epic will aways be level 1, story level 0 and sub-task level -1.

Hi @Lisa Paterson Welcome to Atlassian Community! Ignore the numbering, in order to add the initiative as a parent to the epic you have to add it to the second level. If you add it to the first level it means that the initiative will be parent to stories and tasks instead.

No, there is no way on the ticket to indicate which queue it is in. Queues are basically just filters, so you have to check the settings on your queues to figure out why the requests in question is only showing up in all open. Most likely you are filtering the other queues on specific fields besides resolution = unresolved.

Hi @Patrick Poelma, Welcome to Atlassian Community! Yes, that is possible. You have to look at your customer permissions and set it to only allow agents and admins to add new customers. This will prevent customers from seeing all your projects and you can then add them to the ones that they should have access to. 

What controls if an issue is considered done in a sprint it when it is moved to the column furtherest to the right on the board. So you would have to configure your board so that the Invalidated status is in that column together with any other statuses that you consider as done.

Hi @Randy Pyle, Welcome to Atlassian Community! Sourcetree does not support SVN. It used to support Mercurial, but that was discontinued a couple of years ago and it is now a pure Git client.

You could do this using automation and REST API that query currency exchange rate data. The automation would trigger on when the other field is updated and then get the currency rate via a web request. The returned data from that request can then be used in a smart value to calculate the USD rate.

First off, you could remove the If: CQL condition since the branch will only return pages. Second, take a look at the audit log and see were the automation stops, I have a hunch that it may stop on the if condition.

We need to know what you are doing in that step in order to help you further.

If you can add a screenshot on the Edit issue fields, similar to this:

That KB is only applicable for Jira Data Center, not Jira Cloud. On Cloud the corresponding feature is Themes.

Just to add to @G subramanyam answer, public links are currently not available, Atlassian paused the rollout and is currently planning to make it available in Q4 2023 based on the public roadmap. For Wordpress there is an app by K15t that would allow you do this, it is currently in beta.

You need to uncheck the "Only include issues that have changed since the last time this rule executed" on the branch component, otherwise it would only update linked issues that have changed since the last execution. If you leave it checked you will end up with scenarios like the one here where 593 is not updated because…

You cannot have multiple starting statuses. Since you want type A to have a different starting status from type B you can do that by creating different workflows for the different issue types.

Hi @Nivi Jayasekar, Welcome to Atlassian Community! You can access the dark mode by clicking on you avatar and then select one of the four modes available.

How is the edit due date step configured? If the due date is cleared out my guess is that the value you are setting it to is empty.

Yes, that is possible by adding a workflow condition to the transition, there are multiple conditions that you can use like user in group custom field.

Hi @Patryk Mucha, Welcome to Atlassian Community! The short answer is no, you cannot have a section in the form that just a subset of users can fill out. The workaround that we are using is that when the request is submitted a second form is attached to the request via automation that our team is filling out. 

Use the manual trigger from issue option to make it show up under Automations on the issue.

Hi @Rajesh Patel, Welcome to Atlassian Community! It is only manually triggered automations that will show up there and any automation that was triggered by the issue. If your automation is set to manual, make sure that you belong to the group that you configured the automation to be visible for. 

Both of those two automations are pretty simple ones. The second scenario you can trigger on when the issue is transitioned to Open and then just change the condition to check the issue type is a bug. Then edit the assignee, ether via the edit issue field, or the assignee and you can see in the second one. The first use…

No, the customer notifications cannot be configured by an individual customer to only receive some of them. The only thing they can control is if the should receive notifications or not for a request. 

Hi @Whitney.Hirani, Welcome to Atlassian Community! There is currently an active incident that is affecting Confluence, you can find out more information if you go to status.atlassian.com 

@Anton Chudaev Halp has been discontinued as a separate product and Atlassian stopped selling it as such in May of this year. Going forward it will be bundled with JSM as part of the new Virtual Agent. You can see the announcement here.

You can do this by making a copy of the existing workflow and the workflow scheme. Associate the new workflow with the new workflow scheme and then go to one of the projects and associate it with the new workflow scheme. You can now make changes to the the separate workflows without affecting other projects. 

Hi @Ashish Bajaj, Welcome to Atlassian Community! Are any or all of these projects that you added to the gadget team-managed projects? That would explain why you see duplicate statuses, since team-managed projects are like an isolated island (for now) and statuses are unique for that project and the gadget is using the…

Hi @Lizzie Oldacre, Welcome to Atlassian Community! The project you are using is a team-managed project and in those projects sub tasks are known as child issues and that is why you see that button. If you compare it to a company-managed project you will see that the button refers to sub-task instead. There is no setting…