Hernan Halabi Community Champion

I'm not in front of the computer to add a screenshot but you should find that where you setup the automation rule name

Hello @Nivedita R welcome to the community. There is no problem to use your own custom fields instead of tasks and stories. It would be different if you would be considering replacing epics. You just need to make sure that the story points custom field has a valid context for the new issue types in case you are using it.

Hello @Samuel Bar you can add a condition to the transition that can only be done by a certain user or role. You would add the user assigned to automation and that should do it

All Atlassian apps are based on the amount of users but consider the following. If you add your customers to Confluence all other apps plus confluence price increases, so the more customers the bigger the cost. With the app you pay for your users the but you can grow in customers and price shouldn't increase. Both…

Right, the app doesn't work either? Since you would be sharing external links customers should not need to be users

@Kyle Roberts-york maybe I missed that part of the problem if even after saving and refreshing the sla page things are as they were, I suggest you file a ticket with atlassian support directly as that's not part of the expected behavior and won't be much to do from here.

hello @Fook Lee sorry for the delay on the response. What do you mean by If only supports all match? I believe that's the purpose of the else scenario to have the OR scenario. Can you share your automation rule to see if I can better assist you?

@Mornay Smith sorry for the delay on the response, did the upgrade actually help to overcome this issue or still need help with the troubleshooting?

hello @Kyle Roberts-york what happens if you transition the issue out of that status and then move it back to where it was? Still get the pause icon? Have you ensured that there are no two status with a similar name? The steps described seem to be ok 

Hello @Eric Trucco welcome to the community, you don't have plenty more options. I know there the following app in the market that I believe it can help you achieve this but haven't used it yet https://marketplace.atlassian.com/apps/1220562/external-share-for-confluence?hosting=cloud&tab=overview

Hello @Mohamed Kandil welcome to the community. If you are using cloud then you can't. You would have to migrate everything to a new instance to achieve what you need.

hello @Jawed Ali in order to do that you must have edit all worklog permissions at the permission scheme. It is usually the case that whoever is the project admin can do that but it's not necessarily the case. The permission I mentioned is the one that defines that. 

You should have different screens for create edit and view. If you leave those fields only in the view screen, they will only be visible after the transition in which you fill them 

Hello @Crisan Hristea Carolina Sarah I'd you want to show the fields filled you must add them to the screen assigned to the view option in the screen scheme associated to the issue type. See more here https://confluence.atlassian.com/adminjiracloud/associating-a-screen-with-an-issue-operation-776636488.html

@Arthur Harutyunyan as I mentioned you in your previous post you can achieve this with eazybi but if you are still looking for a free solution I'm afraid there aren't any at this point.

Hello @Sanjay Vani welcome to the community, I suggest you start by checking the Atlassian free trainings to get you started. https://training.atlassian.com/free-training-catalog

Hello @Philip Kroos - TEAM XALT welcome to the community. What you are seeing are the valid transitions, in a workflow you can change the order of them using advanced workflow properties. I would expect that will be reflected in the kanban board as well See this Link…

Hello @[deleted] personally I haven't noticed difference between the different plans

great, please don't forget to mark this as solved then. Regards

And licenses show ok if you go and check it?can you send some screenshots?

I'm not a developer myself so I would be lying on things that you must do to achieve it. On the following link you should find useful information https://developer.atlassian.com/

@Mornay Smith the error might not necessarily come from Jira service desk, specially if you checked the license and says it's ok (make sure you didn't exceed the agents number). Another thing causing the error could be an app that is part of the workflow transition setup that need the license reviewed/updated

its the one I know but you can check this other https://marketplace.atlassian.com/apps/1221587/bmc-remedy-integration-for-jira?hosting=cloud&tab=overview If you intend to avoid apps, you will have to build your own integration solution with webhook and rest API I would say

Hello @Ravi Gunaratne welcome to the community. There is no way to copy everything you mention. I would rather have one active project over the years and if you are really interested on archiving old issues have a second project to do that. Later with queries you can filter years and issue types.

Hello @siva kedari veerla you need to use an additional app. I know you can do it with connect all but might be others as well https://marketplace.atlassian.com/apps/1220859/sync-bmc-remedy-with-atlassian-apps?hosting=cloud&tab=overview

Glad to hear it, please don't forget to mark this as solved to better help others with similar questions

Since quick filters restrict more the query maybe your board should bring all the projects/teams you care and use the quick filters to hide them from the view. In the end should be as if you are bringing them but actually will be the other way around

If the intention is for someone to check each member activity, you would have to create on dashboard per user. If this is meant to be used by each member to know their assignments , you can have only one dashboard and make the queries within based on the active user. The second case is the most common scenario

Hello @Ciara could you please share what settings did you check? The most common case is that even though users are listed to be notified when a ticket is closed they don't get the notifications because the workflow doesn't have the event in place, therefore the notification never happens

Hello @Landskap welcome to the community. I believe you are looking for this https://support.atlassian.com/jira-core-cloud/docs/what-is-a-jira-dashboard