Hana Kučerová Community Champion

Hi @Sergio Garijo Contreras , welcome to the Atlassian Community! I recommend you to contact the vendor of this application and ask directly them - it is up to them, what they do in the future. Usually when some application is successful, it becomes paid.

Hi @Hoyeon Shin , welcome to the Atlassian Community. What is suggested in the provided article: * create a new target project * move every issue from the original (source) project to the newly created target project To your questions: * If you move all the issues to the newly created target project, the original project…

Hi @Baharul Islam Mazumder , welcome to the Atlassian Community! I would recommend you to use Jira Automation functionality and it's action Send web request. The reason is this way you can easily see, whether the request has been send (using audit log) and you can also work with the response, which is not possible with…

Hi @Troy Chaplin , I'm not sure which version of Insight do you have and which endpoint do you need, but have you tried resultPerPage param in combination with page param? I've found it in the iql endpoint documentation.

Hi @Gianluca Galletta , welcome to the Atlassian Community! I believe you are referring to the Tempo JQL functions, the list of available functions for cloud is here. Probably you need to use: "Name of Customer"Account.customer =<span> </span>

Hi @Jaroslav Jaroš , welcome to the Atlassian Community! Email limit is used in two cases: * if you are on a Free plan * If you're trialing Standard, Premium or Enterprise plan (in this case you can ask Atlassian support to disable it) I believe every email counts, no matter who is the receiver. Info can be found here.

@zoe zhang Please be aware I don't work for Atlassian, so I don't have such information. The only roadmap I know about is this.

@asad No data at all. The part of the REST API request is authorization of the user and when you are disabled, you won't get any data.

Hi @zoe zhang , welcome to the Atlassian Community! I believe the only possibility is what you've found - Get Postmortem Request (you need to provide Postmortem id), there's no endpoint for getting all Postmortems.

@asad Yes, you can't get it. It would be serious security problem, if it is possible for disabled accounts to still get data (no matter how).

Hi @asad , no, this shouldn't be possible. If you cannot log in, it is not possible to get issues, even through REST API.

Hi @Daniel Tveriya , it depends on how your SLA is configured, there can be different conditions in each of your JSM projects. Please see here for more info ("Finish counting time when" condition).

Hi @Marcin Wiktor , welcome to the Atlassian Community! Have you also checked legacy automations (not only the "new" ones)? 

Hi @Lavanya Badagala , welcome to the Atlassian Community! Yes, the board needs to have some location (project or user). If you are not Jira admin or admin of this board, you need to ask these users to fix this (see here).

Thank you for the clarification @Suporte JRetail . These are linked issues and it is standard functionality available for every site. In that case your automation rule will be something like: When: Issue commented For: Branch rule / related issues: Linked issues (Link types: is caused by) Then: Comment on issue (In general…

Hi @Suporte JRetail , what exactly do you mean by "attached item"? Linked issue by some specific link to the commented issue or something else? Thank you.

Queues can be starred, so maybe you can tell your agents to star only the queues, which are relevant to them, but you cannot hide them completely from them.

Hi @Jouni Riimala , in general you should be able to do it, but with the usage of conditions in automation rule. Something like: If: Issue Type equals User Requirement Then: Edit issue fields: Summary = UR - {{issue.summary}} Else-If: Issue Type equals Story Then: Edit issue fields: Summary = ST - {{issue.summary}} ...

Hi @Evert Morren , AFAIK this is not possible. May I ask you why you need such a functionality? Maybe there's another possibility how to solve it. Thank you.

Hi @Sreenatha Reddy J , AFAIK this is not possible in cloud. You can create screen with both fields (date + reason) and enable to edit these fields only during some transitions together, but still you cannot force user to fill in the reason field if date field is changed.

Hi @Geetha , welcome to the Atlassian Community! I would do some sort of analysis, in which projects these additional fields are used and why and try to get rid of these additional story points fields and keep only one original field. I don't know how big is your Jira (how many projects and issues and affected), but it…

@Neethu Johns Have you tried to contact Gurock Software?

Thank you!

Hi @Golla Sathish , which changes do you want to discard exactly? If you have any problems with your roadmap, I would recommend you to create a new question, this one is quite old.

Hi @Neethu Johns , would you provide more information, which application is this? It doesn't look like core Jira functionality. Anyway, if this is connected to some application, I would recommend you to contact vendor of this application, because without logs we probably won't be able to find out, where's the problem.

Hi @RAJESH , the only possibility I'm aware of is usage of workflow properties, something like: jira.permission.comment.projectrole = project role id

Yes, I helieve it is still not possible, there's open issue for this: JRACLOUD-75868

Hi @Ged Dunn ! So, in your case, when you create Jira backup for cloud: * Yes, all the previous data in Jira will be lost and replaced by the data in the backup. * - 3. Yes, you can import it back, but be careful. A lot of things are not part of the cloud backup, usually apps data are stored at vendor.

Hi @Rahul Kumar . Yes, that is correct.

Hi @Colum McAndrew , originally I used JQL: status changed to XXX BEFORE YYY But this wasn't working correctly, because in our case issue could get to status XXX repeateadly. So, I ended up creating new Date custom field, where I store the date, when the issue was transitioned to status XXX for the last time. Then I use…