Comments
-
Hi @Lenka Havlíčková , probably some sort of filter is applied, so you cannot see the cards. Please try to hit 'x' on your keyboard to remove this filter.
-
If something goes wrong, please, let me know, I will try to help.
-
Hi @Colum McAndrew , yes, I think this is a good plan. We did very similar thing.
-
Hi @jun lee , I believe the problem is you are creating two linked issues with link "contains/is contained in". (and not child issue for some parent). This is the reason why the automation rule is not working, because there's no parent for your created issue (only linked issue). I think you need to use different approach…
-
Hi @Mor , welcome to the Atlassian community! It is possible to use JQL: assignee changed after xxx But you need to replace xxx with some specific date or time function like startOfDay(). The only other possibility I'm aware of is create your own JQL function with SciptRunner application.
-
Hi @Davin Studer , I believe these need to be created as remote links, see here. Request body will probably look something like this: { "globalId": "appId=your-confluence-app-id&pageId=your-confluence-page-id", "application": { "type": "com.atlassian.confluence", "name": "your-confluence-name" }, "relationship": "mentioned…
-
Fantastic! This is something I really appreciate!
-
Hi @ARabade , AFAIK Insight Discovery is a scanning tool, which collects data from your enterprise network and store them as files to your infrastructure. You can import these files to Insight, which is part of Jira Service Management Premium cloud, where you can choose Data residency (Australia should be available). So, I…
-
Hi @Ушков Антон , welcome to the Atlassian Community! It should be available immediately after you remove the last team managed (next-gen) project. Could it be the team managed projects are still in the trash and not deleted completely?
-
Hi @Shashank Agrawal , in the same manner you should be able to do something like: issuetype = Sub-task and parent = {{issue.key}} When I need to work with Sub-tasks, I usually use Branch rule instead of Lookup issues: New brach -> Branch rule / related issues -> Type of related issues: Sub-tasks.
-
Hi @Aya AlJboor , yes, there are differences, please see here.
-
Hi @Jon Jerman , please navigate to the detail of your balanced workload automation and there should be a checkbox: Allow rule trigger - Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule. Is this checkbox checked? Thank you.
-
Hi @Eduardo Tavarez , yes, automation functionality can help you with this. Boards only visualize data from projects, so you need to figure out, to which project exactly you need to create the issue, so that it shows on your board B. And also in which project the transition from X to Y needs to be done.
-
Hi @Petra de Vaan , welcome to the Atlassian Community! Definitely, monthly billing (NOT annual) is the right choice for you.
-
Hi @John Sheng , please try something like this: { "fields": { "summary": "Sub-task of TEST-101", "issuetype": { "id": "5" }, "project": { "key": "WDEXTEND" }, "description": { "type": "doc", "version": 1, "content": [ { "type": "paragraph", "content": [ { "text": "Don't forget to do this too.", "type": "text" } ] } ] },…
-
Hi @John Sheng , please, which REST API endpoint are you using? Which instructions are you following? Thank you.
-
Hi @Sriram Kancharla , welcome to the Atlassian Community! Yes, I believe both topics are revelant, for example see here. By template it is meant that you use template created by Atlassian, not that you can create your own template.
-
Hi @Byron Barker , good news - I've got this functionality available now. What about you :-)?
-
Hi @Ilia Naumov , welcome to the Atlassian Community! If you are purchasing Jira application, the number of users is based on the major Jira product. For example if you have: * Jira Software - 250 users * Jira Service Management - 50 users you need to purchase the app for 250 users. It is not possible to purchase the app…
-
Hi @DPO OETC , welcome to the Atlassian Community! I believe the reason for the limit is the spammers were creating free cloud sites and they were sending a lot of emails through it. I believe I've seen some article about this, but I wasn't able to find it anymore. Limit is 100 emails / day, see here.
-
Hi @Alon Shoham , welcome to the Atlassian community! There are two possibilities: * Annual billing, which means your are paying for user tier 26-50 (and it doesn't matter if you have 26 or 40 or 50 users) and you pay at once for a whole year * Monthly billing, which means you pay each month the price according to current…
-
Hi @Vinay Sharma , yes, there are limitations, it depends on your Jira plan, see here, section Automation. Another useful links: * How is the usage calculated * View automation usage
-
Hi @Florian Nawrath , welcome to the Atlassian Community! Unfortunately I believe the only possiblity is to split the object types as you've described. It is possible to use a “hidden” property on the attributes, which allows you to hide attribute from the Insight users role, but this won't probably help you.
-
Hi @adithya , yes, it is possible, please see here, section How to mention another user.
-
@Jack Brickey Please, have you found out anything? I assumed this is JSM project. AFAIK there are no internal comments in JSW projects. Thank you.
-
Or alternatively you should be able to test, whether the comment is internal or not, see here.
-
Hi @Michael Cheng , maybe you can add User condition to your rule, something like: User: User who triggered the event Check to perform: is a customer
-
I believe I understood your request before. I don't think it is possible.
-
Hi @haarika_cont , if you want to create issue in project ANI with an issuetype from project SSD and this issue type is not allowed (which means it is not part of the issue type scheme), you won't be able to do it. You have to first add this issue type to the project's ANI issue type scheme.
-
Hi @Prateek Verma , welcome to the Atlassian Community! AFAIK this doesn't work like this. Time should be automatically logged in to the issue, but these are not Jira comments, so you won't be able to see the information in the comment section.