Prince Nyeche - ELFAPP Atlassian Partner

You can use automation for Jira, specifically the schedule rule and set it to run daily. You can use this JQL Project =ABC AND status = "Done" and updated < -30d Then set an action to delete the issue. 

Hi @Anna Gulina There's no limit to the number of project creation you can have on Jira. Also there's no limit on the number of collaboration your user can have on one project or multiple projects. Your Jira users collaboration depends on how many licenses you can purchase. On the other side if you use JSM for customer…

Something in this nature, you need to do in the email template you're using to send. final emailTemplate = """ Hello user 1. Issue key: <a href="https://mydomain.jira.com/browse/${issueKey}" target="_blank">${issueKey}</a> 2. asignee: ${asignee} 3. Due date: ${dueDate} 4.Summary: ${summary} """

I think that might be a bit of a manual work now.

You need to find this icon, if you can't use it most probably you don't have the permission.

Hi @Teja Sorry, didn't see the server tags. You don't need accountId if it's server. I believe the approach I would use here is retrieve the current custom field value in a list, then create a payload that contains the old value and new value, then update the custom field with both values.…

The problem here is that those child issues might most probably be orphaned now or depending on your configuration it would still be attached to the child issues as Epic can still have sub-task issues. You should check the issue view and see if the sub-task are listed. If it's not, check the issue history of the parent to…

Manually by viewing the ticket click on the watcher icon (Project permission applies) or you can automate it by using automations. The latter can be tweak by issue types but will have static values.

Have you tried the Jira cloud for sheets or Jira cloud for excel addon both free on marketplace to get more than 1K issues. 

You can't lock any fields on Jira by configuration. Only certain system fields are locked and it because you are not suppose to tamper with it. Is there any particular reason you're looking at locking such field?

I believe email is sent in a html body, so can you define the <a href> tag and append the issue key there with a default url such as "https://mydomain.jira.com/browse/${issueKey}". So once you receive the notification, it can have the link embedded?

You will need to get the accountId for any user picker field, then you can append that. That will involve you searching for the users from your user base.

I think you need to be on Atlassian access to use those features (of email change) and definitely, since your domain is already claimed, those users can't manage their own profile anymore.

You will need to enable your Jira webhooks from Settings > System > webhooks. Connect to a webhook receiver that can receive the json payload based on certain events. Remember webhooks in this context is sending out of Jira and not receiving to Jira.

First of all, you need to find the field by using the "/rest/api/2/field" endpoint. Then you can use the api for context option to get the options. I'm assuming during the first search, you are filtering for the type of custom field you want.

As much as you want.

There's a free app I made on marketplace that does just that using CSV.

Hi @Ron Sanders There are multiple approaches to migration. It also depends on which one you think is less risky in your Org based on what you've researched so far. You can opt to use * CSV import * JSON import * JCMA If you think those methods are time consuming, you can get help from an Atlassian partners to assist with…

Hi @Vivek Gupta This is as a result of GDPR and that's the expected behaviour on Atlassian cloud. If you require access to an email, it is either you're using a connect app which in turn you must have made an official request to Atlassian for the email API otherwise via your standard REST request the emailAddress field…

You will need to review the documents to know how to do that and typically apps on Atlassian Marketplace needs to be approved before they can be searchable on the store.

Hi @Surya A You can start from here and it also gives a basic example which you could try.

Unfortunately no, you can't reset it. This is something only support can do but your current tier prevents that. What you can do is temporarily upgrade to standard, get support and change back to your free tier. However please note that you could be billed in a prorated manner. 

Another thing you could do, is create a report of each ticket which could let you know such information. I wrote this article here a while back that can generate such a report but you have to use API to achieve it.

Support is not available for free accounts.

Hi @Prabhu Prabhakar I think @Alexander Bondarev has explained the problem. Your users should know how the application works and not the other way around. You trying to force a feature into an application that doesn't do it is a waste of time. So the earlier you explain the situation, the better.

JQL won't be able to filter a comment by the reporter especially when such reporter can't be specified. You will need to look into an add-on from Atlassian Marketplace that can do that.

Remove it and see what happens!

Hi @srinivas kolaparthi Why the comment #params=query, on the response?

Hi @Marcos Milanesio Can you also check other solutions mentioned on this post 

Hi @Nishant Sharma This is an article I wrote a while back, it gives a thorough understanding about Jira webhooks.