Arkadiusz Wroblewski Community Champion

@Венера if you are using Create issue and not Clone issue, then I would not expect the native clone behavior to help here. In that setup, Automation is creating a completely new issue in Project B and trying to carry over the Assets value from {{triggerIssue}}. That is a different scenario than standard clone-based field…

Hello @Rolf Breuer if this is Confluence Data Center, then as far as I remember not natively. Anyone who can view the page can also download the attached files, and Atlassian’s DC docs state that there is no separate permission just for attachment downloads. So if the requirement is “can read page, but cannot download…

Hello @Harshveer Kaur I think this is usually less about creating one special read-only profile, and more about separating what kind of access the user really needs. In practice, I would split it like this: if they only need JSM portal access, that is one model if they need to open the Jira project itself, that is a…

Hello and welcome @Венера I have a pretty similar use case, but I solved it a bit differently. If you are really cloning the issue, and not creating a brand new one from scratch, then I would first try the native clone options in Automation. During the Clone issue action, you can already copy field values from the original…

Hello @Babar Brohi @Trudy P Claspill is right that it really depends on the organization, but since you tagged this as Jira Service Management, I would say your use case is probably a bit different from the usual “software teams sharing boards” discussion In JSM, I would usually lean toward separate service projects when…

@Chris Rainey @Himanshu Tiwary Haha, absolutely the Atlassian admin golden rule. 😄 Half of the “Jira is broken” moments usually turn into “oh… that automation did it” right after checking the audit log. I’d be happy with any Atlassian T-shirt or basically any swag at this point, because my company seems to think it’s…

@Prince Nyeche - ELFAPP very nice article. One thing I would definitely add from experience: every migration is a bit unique. The overall phases are absolutely right 🙂 preparation, execution, stabilization but the real complexity usually comes from the details of that specific instance: old workflows, app dependencies,…

Hello @mgupta from your description, I would first check whether the rule is doing a JQL search and then iterating through each returned issue one by one. If yes, then the problem may be less the email action itself and more that the rule scope is simply too broad. A broad JQL combined with a loop can consume Automation…

Hello @Robbie from my Experience, the public JSM knowledge base is quite limited here. You can group articles into categories, but I would not expect a true multi-level category structure there, like category → subcategory → sub-subcategory, at least not natively. So if your goal is to build a deeper structure for users,…

Hello @backoffice In this case, please submit a request directly to the Atlassian Billing team, as we cannot provide billing support here in the Community forum.

Hello @Dominika Goliszek I understand your case, but this is a Community forum. The best help will come from your organization admin, since we cannot see your company’s internal settings here.

@Manoj So yes, removing that property was the right next step. The remaining behavior looks cosmetic/UI-related rather than a rule problem.

Hello @Manoj From the error shown, I would probably look less at the date format itself and more at whether Closure Date is actually editable in that specific context. The key part is: "Unknown fields set during edit for Closure Date" In my experience, that usually points to one of these areas: * The field is not available…

Hello @Anuradha Bista Failure seems to be generic. Please try logging out, using a private browser window, and waiting a little while, as sometimes it is just a temporary hiccup.

Hello @Bettina Schierholz From a security/privacy point of view, you should assume the sandbox may contain real production content, including comments, attachments, employee/customer data, and KB content, unless you deliberately limit what you copy. Atlassian confirms comments, media attachments, users/groups, and…

@Ashok Murugesan for the use case you described, there´s not a free read-only Jira/JSM project user today. If your clients need to open the project and view historic issues directly in Jira, that is still basically Jira-side access, and that normally means a licensed user, even if you restrict permissions to read-only…

Hello @FrancoB The Key for cascading fields are correctly referencing values from another field. It all depends on your specific use case.

Hello @Ashok Murugesan it depends a bit on what you mean by read-only. If you mean a portal-only customer, then no, that does not require a paid JSM agent license. Atlassian’s current licensing docs say JSM is licensed by agents, while customers can access the portal for free. If you mean someone who should access the…

Mine was realizing that “just one small automation” is how Jira admins accidentally start a second full-time job 😄 So my habit now is: If a rule needs a paragraph to explain it, it is probably too clever already. Keep workflows boring, keep automations small, and always check the audit log before blaming Jira. That one…

Hello @Carlos Puente that definitely sounds like the rule is acting on too broad a scope / wrong issue context. From your description, I would say the most likely cause is that the automation is not really tied tightly enough to the currently opened ticket, so it ends up running against the previously selected issue…

Hello and Welcome @koen for me, the best use of Automation is to take care of the small, repetitive things that nobody really wants to do manually all day 🙂 So I would usually approach it like this: keep the workflow itself as clean and simple as possible then use Automation for the repetitive admin work around it Typical…

Hello @arjun.nagaraja My biggest suggestion would be: start simple. With Assets, it helps a lot to first define: which object types you really need which attributes matter and how those objects should be related to each other A lot of people jump straight into imports, but usually it is better to get the schema / object…

Hello @ckopanon if this is about internal notifications in JSM Cloud, then usually no, not really in the built-in template. Customer notifications are the ones you can customize much more directly. Internal notifications are handled separately, and Atlassian’s Cloud docs pointing focus is more on who gets notified / on…

Hello @ckopanon If you mean the internal / agent-side emails, those are usually driven by the Jira notification scheme, not the customer notification templates. So I would first check whether the relevant event is actually configured there, for example: * Issue commented * Issue updated * Current assignee / watchers /…

@Ajay _view26_ I wonder if this all Questions lately about things which suddenly not working at service management projects are not tied to release Service Collection and some changes.

Mugs always 🤭 Coffee needs to land somewhere 😂

Great to hear that. You welcome. Have great day ☀️ 

Hello RC_Riley@rush.edu You asked us and @Mikael Sandberg a tricky question 😅 This thing can answer probably your..... Admin or Support. Yes I know that sounds like joke but that's true 🤠 Have great day ☀️ 

@Siobhan O_Leary Donkin Not directly, but some users may be able to flag a topic for Atlassian Support. Until then, please try raising a support request yourself. If 2 users cannot see it but 1 can, this does look like a permissions issue. That said, someone really needs to review the whole setup directly, because from the…

@Trudy P Claspill @Marc -Devoteam- Can one of you Mark this Topic for Atlassian Support ? @Siobhan O_Leary Donkin Alternativ you can reach out to me on Linkedin for a Small Debugging session.