Mikael Sandberg Community Champion

Hi @Soroush_Heydarian, Welcome to Atlassian Community! In order to be able to edit a page the user needs to have edit permissions on the space level. Page restrictions is just that it restrict how can edit and view a page, it does not give you those permissions. Confluence has three levels of permissions, global, space and…

Hi @Sedat Demir, Welcome to Atlassian Community! No, as of last year you can no longer buy new Server licenses. You would have to upgrade to Data Center which has a minimum of 500 users or migrate to Jira Cloud.

It all depends on how your custom field is set up. Since you are mentioning Incidents, are you looking to add multiple services to Affected services? If so, that is currently not possible because that custom field is locked and only support a single object. A workaround would be to create a new Assets object custom field…

You should be able to do that using automation rules. Have a look at the documentation, Configuring Assets automation rules. It has been awhile since I used assets on Data Center (Cloud doesn't have automation rules within Assets) but if remember correctly you can do that using the HTTP request THEN action.

Hi @Chris Thomas, Welcome to Atlassian Community! If you are using the default ITSM project your Incident requests should have a field called Affected services, that field is linked to services. If you do not see it on the request then you can always add it. Just go to Project settings > Request types > Incidents and then…

You would need an app in order to access external data in Jira. What type of data are you trying to access? Have a look at the Marketplace for apps that allow you to populate custom fields with external data.

Hi @Sandra Middleton, Welcome to Atlassian Community! There is, but you need Jira Software Premium in order to get access to Advanced roadmaps, or you would need an app from the Marketplace that can do it. The roadmap that comes with JWM can only be used for a single project. 

The JQL is simple: status = Done AND Resolution = Unresolved Since you are running the automation in a single project you can leave that out in the scheduled rule.

By the way, here is the product release note about it, as you can see this started rolling out in January 2023.

This is a new feature that is still rolling out, so if you currently do not see it you should see it soon. Sometimes the documentation is describing features that have not yet hit every customer.

This is expected behavior. When you are searching on label != X it will only search on issues that have the labels set to something, and that is why you have to include labels is EMPTY as well. Same thing if you would have a search that excludes a component, you would then have to include the empty ones as well.

Hi @Laura Njombua, Welcome to Atlassian Community! It is possible with automation, the question is do you want to do this association when the release is created or when the issue is created? The first one is the easiest one since you would trigger on version created. The second one would be a bit more complicated since…

Another option besides of what @Trudy P Claspill is suggestion is to use an automation to bulk set the resolution for the issues that are already in done. Create a scheduled automation and set the JQL to one that select all those 177 requests, and use the edit action to set the Resolution. Once you published the automation…

No, because the functions that allow you to get start of day and end of day follows the 24 hour clock. So in order to get issues between 17:01 and 17:00 the next day you have to use specific dates. There are apps in the Marketplace that extends JQL with more features, but I don't know if any of those allows you to search…

You would have to use a JQL with specific dates and times in order to do it, something like this: (created >= "2023-02-03 17:01" AND created <= "2023-02-04 17:00")

Hi @Clayce Rodamer, Welcome to Atlassian Community! As you have found out it is not possible to add additional fields to the work log screen without an app. 

Hi @Paul Shinn, Welcome to Atlassian Community! Based on the second URL it leads me to think that you are using Jira Service Management, is that correct? Users that do not have a JSM license assigned to them, and only have a Jira license, are not allowed to access the queue view, so you would either have to assign them a…

So the example is pretty simplified. If I would implement is it I would use a different link type, like composed of/composes and also add in a check for the required field for ticket A. That way you limit the number of false positives. What the If: Linked issues is doing is checking if the linked issues, in this case your…

The portal is looking at the Resolution field to figure out if the request should be shown as open or closed. So in order to show Resolved requests the resolution has to be set to None, so you should not have a transition screen when moving to Resolved that has the Resolution field on it. Instead you could add a circular…

In that case you cannot use automation, since rules are triggered after an action is taken. You would need an app that integrate with the workflow, like Scriptrunner or JSU Automation. There are other apps in the Marketplace that can do that, these two I have used in the past.

That condition looks correct. If you look at the audit log, what does is say? Does it pass the condition?

Setting the default issue type will only affect the first time you click on create. The next time you click on create it will remember the last issue type that was used, which is expected behavior. There are two suggestions that you can vote on to change this behavior, JRACLOUD-74771 and JSWCLOUD-17743 

So regarding blocking issue A from being closed, the automation would look something like this: Note that this is just an example and have not been tested, and I would probably use a different link type as well. Yes, your tasks can be moved to other projects after they have been created, just make sure that any automation…

Hi @Dmitry Panov, Welcome to Atlassian Community! Yes, automation can create tasks, and would look something like this: In this example I used Priority as the field to check, just change that to your custom field.

Anyone that have access to Jira and can access your JSM project can view the requests and add internal notes. Check your permission scheme for the JSM project to see if you allow anyone to browse the project. The default is to only allow the project roles Administrators, atlassian-addons-project-access, Service Desk Team,…

Yes, that is possible. All you need to do is add an condition that checks the issue type. If the issue type is not part of the list the automation will not proceed past that step.

In JSM it is only the agents that needs a license, your customers do not need a license. Have a look at this FAQ for more information. For license cost information, go to the JSM pricing page.

Hi @Dinara Kurmakaeva, Welcome to Atlassian Community! You can set the default issue type of you go to Project settings > Issue types and click on Action > Edit issue types. Once you set the default issue type, do not forget to hit Save for the change to take effect.

You can't remove those, those are apps that are installed on you instance, and in the majority of the cases when it comes to apps they cannot be configured to a subset of projects. The only thing I can recommend is to contact the app vendor and suggest that they add a feature that allows you to select the projects that the…

Confluence doesn't have a smart value for last viewed currently, it only has it for first published and last updated. You could use the Give feedback under the Help section in Confluence to suggest that they add smart values for last viewed.