Matthias Gaiser _K15t_ Community Champion

Hey @Phillip C I have some tips which we've checked out for our own automation rules: * Make sure that the first action in your rule is a condition which executes this rule only in the necessary cases. This way the rule results in a "No action" result and therefore doesn't count against the limit. * Depending on your use…

Hey @Eddie's Day I think in this timeframe, there was a change in Trello that every board which was not assigned to a workspace was closed automatically. I remember we had to reopen quite some boards. You can check out if your boards were simply closed and reopen them. Here's the documentation how to do that. Cheers,…

Konichiwa @Hiroko Ishimaru I'm afraid my Japanese is not really better than that. From an online translator, I understood that you're searching for how to set a due date. Maybe this help article can help you. If that doesn't work, can you be more specific? Cheers, Matthias. Automatically translated version: コンニチハ @Hiroko…

Hey @Hancheng Lvsiqing by default every edit to an issue results in possible email notifications depending on the Notification Scheme used in your Jira project. If you disable this checkbox, Jira won't send email notifications for this issue update you configure in this automation rule. The email will be sent according to…

Hi @Mike Prill some time last year I gave a talk about cross-company collaboration with Jira which mentions several ways how you can collaborate with external people. In your case, I think an external issue share app would work best. There you can create links for single or a set of issues which you can share with the…

Hi @Doug Winenger the error message "data was not an array (customerfield_123456)" sounds to me like you did not provide an array of users but only one user instead. Is it possible that your user field is a user field which allows to define multiple users in there? There's a custom field for single users and also one for…

Yes, they moved it back, but I've also asked for a deeper investigation/explanation as you did.

Yes, you're right, @John Baker. I meant rule configuration 🙃. Thank you also for sharing your use case. I'll make sure to share that with our Scroll Content Quality team. And of course, you're welcome to bring colleagues along.

@Mark Rekveld - Marvelution, unfortunately no news yet. But I've used this occasion to ping them again.

@Kevin Bui - it would be great if you can also update your documentation with the planned pricing changes so that users are aware of it.

That's correct, @Thierry Dalon! To share the full story: All new Atlassian Cloud instances end with .atlassian.net. There are also some older ones around which are years old, e.g. our support Cloud instance, k15t.jira.com. But as a good enough criterion for now, you can say if it ends with .atlassian.net. Until Atlassian…

I'd still go ahead and use the name property to display them. Subtasks are a bit different because in Jira's UI, it's not only showing the value, but also resolving the actual issues in to clickable links. For other fields, the name property should be what you want.

@John Baker, on another note. We're planning some updates to the role configuration experience. Would you be willing to jump on a call with us to share your thoughts and we can possibly share some of our plans? If so, please schedule a call here.

Hey @John Baker great that you like our app. 😏 Are there concrete topics in mind you'd like to do more? In case you didn't know, here in our docs you can find all available rule types. Cheers, Matthias.

I can confirm that it's removed again, but I don't see any reasoning for it. I'll reach out to some Atlassian to have a look into that.

Hi @Jacob you're right, you can achieve some cloning and even syncing with Automation. If you want to that way, you need to create automations which listen for field changes and update the other issues correspondingly. I'd use an issue link to keep the relation and then various automation rules which listen for changes and…

Hi @Alka Singh I'm not sure for how many users you'd like to configure this. If it's only a few one way could be to run an automation with a scheduled trigger. Add a Lookup Issues action to search with a JQL like "assignee = 12345 and updated > -14d". As a third step, you can send the automated email with the result of the…

Hi @Chayoung Kim usually this happens if someone deletes issues or if issues are not visible to someone due to permissions. (I've read that you say it's not like that.) I'd still advise you to: * take away delete permissions from everyone and see if the problem still occurs. * check out your issue security scheme if there…

Hey @박성민(학해) may I ask why you not simply let the users create the ticket in portal B? There are some ways to use Automation or an issue sync app to copy the ticket over to project B, but the main downside I see is that you lose the communication channel with your customers. Happy to hear your thoughts. Matthias.

Hi @AisM I've written a community article how to configure a project banner in Jira Data Center using the global announcement banners. You can check out the code over there and modify it according to your needs. You may want to do these modifications: * You can either keep it as a banner or modify the code/come up with…

Hi @Abhinandan Maheshwari welcome to the Atlassian Community. There is a REST API endpoint which lists all available fields within a Jira instance including the type information. The url is constructed like this: BASE_URL/rest/api/3/field You can see an example response…

You're welcome, @succeeding. I've just created a space and copied a page with the old editor into it. You can download the csv export here and import it into your Cloud instance as detailed in these Atlassian docs. I hope that helps. Keep in mind though that eventually the old editor will go away (I assume).

Hey @Simon Matthews I believe there is no easy way for this. However, if you're fine in creating an automation which performs a call to the JSM REST API, you can achieve this. I'd sugget such an automation: * When: Issue created * Then: Send web request* You need to call the get organizations endpoint of the JSM REST…

Hey @succeeding welcome to the Atlassian Community. Here's an interesting thread with more details for you, I believe: https://community.atlassian.com/t5/Confluence-questions/Switch-to-old-Editor-possible/qaq-p/1104580 It lists two approaches: * Contact support (which is not possible for you with a free license) * Copy a…

Hey @Dimitri Griparis I had a look at the marketplace listing and it says there that the app is unsupported. I also see that you've posted a question in their forum asking for help yesterday. We at K15t also have some apps which we officially don't support in our Labs account. Our policy is to still support these apps…

Hey @Benjamin Stapleton, thank you for the detailed description of your use case - that helps in providing a good answer. You asked: Is there any downside to this approach? If I understood it correct, people from one team shouldn't be able to view issues in another team's project due to data security reasons, right?…

Can you share how your hierarchy levels look like? How are these levels tied together? Maybe a screenshot helps.

Konichiwa @koutarou ishibashi I'm afraid my Japanese is quite limited, but I tried to translate your post with deepl. If I got it correct, you're searching for an automation to automatically close a parent issue when all child issues are done. Is this correct? There's another template in the automation library which could…

If you're not aiming for emptying every 8 weeks, but just want to hide all issues older than 8 weeks, you could also modify your board filter to something like: * updated <= -8w Excludes all issues not updated in the last 8 weeks * status CHANGED BEFORE startOfWeek(-8) Excludes all issues where the status did not change in…

Hi @lucas_morais according to the tags you've used, you're using Jira Software on Cloud. In Jira Software projects, there's no support for forms. Jira Work Management projects have forms and Jira Service Management projects have the portal view which is also like a form. Could it be that your other projects are either one…