Marc -Devoteam- Community Champion

Hi @rkarnaker What kind of gadgets are you using on your dashboard?

Hi, You can create multiple object schemas (sets of assets), based on attributes in the objects and configuration on custom fields you could use separate data for different customers.

Hi @flim I see, that Issues Type is then part of the Atlassian project template used to create your new project. You can still remove the issue type from the project if you require, by adjusting the issue type scheme used on the project or use a completely different issue type scheme. This will only be applicable on…

Hi @Cam Burridge Welcome to the community. The 'Prompt for input' toggle has the function that when some one triggers the rule it prompt field to be filled. You can't use smart values here. The field you select here are variables you van use on other actions in the rule. Example: When the server team receives a work…

Hi @Jakeer You need to use the custom option. The errors reported, are feedback that the JSON probably not correct.

I would advise raise a support request at Atlassian Support. They might have the answer.

So to understand correctly, your company has 35000 users and all of them require a JSM license?

Hi @Jakeer You would need to use the custom option in the web request and specify the JSON. You can use Issue Data (Jira format as example). But you can't sent this to your other jira as is. The request specifies the issue data and to be created with all the same details as the original issue. But do you have the same…

So as you mentioned, It might that this doesn't work in a loop. I would advise raise a support request at Atlassian Support. The only other thing I could think of is to create a variable where you store the checkbox content and use that variable.

Hi @Axel I see the issue I can only see filters I created or the default ones, or the ones I have starred. This might be a bug or a feature that is not available. I suggest to raise this at Atlassian Support.

HI @Wayne Jolly I haven't seen or found any EOL on this topic. But I think the Legacy Editor will stay active until Atlassian decides to stop using DC installations as well ant they only offer cloud. As currently migration from server or DC will move all pages to Confluence Cloud, but they will use the legacy editor as the…

Hi @changhong When is the last time you used your product? Official Atlassian statement on Free subscriptions Inactive Free products will be deactivated If all the Jira Cloud products on your site are on a Free plan, your Jira Cloud products will be deactivated after 120 days of inactivity. If any Jira Cloud product on…

Hi @Marko Turic Welcome to the community. I don't think this is a possibility in the app. The documentation isn't stating any topic on export/import. So I will say no. You could reach out the the vendor directly and ask if this is a function or might it be a feature that you can suggest.

Hi @flim Assets information is set in the instance and is usable in JSM , JSW and JSM projects. This is all depended on the further configuration. To use asset information you will need to create custom fields to be able to use the information on screens. Check out the getting started guide on assets 

Hi @Axel Its not very logical, but in the Jira app you have to select "view recently" then all filters appear. At least on my phone using the app to my instance.

HI @Víctor Rodríguez Siles Can you try the following. Replace this {{issue.Acciones creación usuarios}} with {{issue.customfield_xxxxx}} where xxxxx is the custom field ID.

Hi @Diya Shrestha Welcome to the community. @Ezgi Bayındır is right on the condition to be used. You should not use Legacy Automation options anymore, as they are less powerful than the new automation options. Best practice is to also change your old rules to the new automation rules option provided by Atlassian.

Hi @flim The last 2 are default issue type from the system. The first one isn't an issue type by default. Can you share where tis is in your system, as I'm not able to reproduce this as an issue type on a default setup.

Nope, this can't be done.

Hi @Montnic on the Clone action, choose what fields to set. You could set the assignee field to unassigned for example

Hi @[deleted] No there is not as this relates to web traffic. You should look at web stat tools, like Google Analytics or Piwik or other. Atlassian is not doing this, as this would cause major implication on GDPR.

There is no remove option via JSON. See post from @Bill Sheboy Checking the metadata show there is no remove or delete option via JSON. You could contact Atlassian Support for this one: https://support.atlassian.com/contact/#/

Hi @Tilman Ulshoefer I would reach out to Appfire the vendor and raise an issue at their end to see if and how this configuration is possible.

Hi @flim I double check on my own instance and made a dummy project and added a cascading field in my queue. Indeed it is not possible to sort on a cascading field. This is not being considered by Atlassian as well, see JSDCLOUD-10438 

Hi @Michael Bohlender My advise would be to reach out to Atlassian Support. they have access to Cloud instance backend, they can check the logging.

Hi @Роман Just check, is the Customer Request Type field set on the issue and is the user relate to email ni.r@mail.ru a customer on the project? If this is all the case it would advise to raise an issue with Atlassian Support. AS it might that the user is blocked on their side, they can check this. This can't be solved…

Then I advise you to raise a request with Atlassian Support.

Hi @Ellen Ruscica Jira has no sub board option ootb. Are you using an app for this in your instance? Or do you mean you have multiple board on one project? If so the filter has to be adjusted for both boards. Each board has a filter, this could be the same filter, so check the filter on the other board. Are you using the…

Hi @Ed Clarke When adding the form to the issue, the form has to stay open and has to be made externally available. Then the user is able to edit it via the portal. The main problem/risk I see here is that the user can also edit the fields set by the agent.

Hi @Adrian Zurawski Hi then probably the account related to the email address is disabled in Atlassian Admin. See this KB article, to help you out. You need site or org admin permissions for this action.