Mikael Sandberg Community Champion

The easiest way to identify those fields would probably be to use the REST API to get the context for each one. Your other option is to go into Project settings > Request types and look at the request form to identify all custom fields that you have added.

Have a look at this article for a potential way of doing it using the REST API and Confluence.

Hi Colleen, Not sure if you found a solution for this yet or not, but you have a couple of options here. It can either be done using automation, using a filter and filter subscription, or a post function that sets the event and then use the notification scheme to send a notification to the users.

It should be instantly, but I'm not sure if the form keeps track of if there is a change or not.

No, it only sets the release date on the version, not a custom field that you have on issues. For that you need an automation, and I would trigger that on when the version is released.

Yes, it is possible, just use the Version picker field type. But you could also use the existing Affects version field, that is what that field is intended for.

To add on to what @Brant Schroeder mentioned, what you could do is have specific queues for different statuses. Lets say you have one that for the current user it is only showing issues that that user is assigned to and only have the status "waiting for support". Once the work is done and the status is updated, either via…

If you set the release date without releasing the version you have to pick a date in the future, and that is why you see that in the automation. When you release a version, it will automatically set the release date for you, so there is no need for an automation. Example: I created release 1.0 with only a start date. Now…

Short answer is no, you cannot reset the issue key number, in order to do that you would have to create a new project.

If you are leaving the form open after it has been submitted you should see Edit instead of Reopen, just click that and that then submit and that should trigger the update of linked fields.

On rare occasions that happens and in that case you need to make a copy of your workflow and then re-apply it to the workflow scheme and that should solve the problem. 

Changing the workflow will affect all issues that is associated with that workflow, it will not just apply to future issues. 

Click on the dropdown menu in the Epic and select Mark as done, this will set the Epic status to done. Note that the Epics have two statuses, the normal status based on the workflow and an epic status. Your other option would be to either create an automation that sets this once the epic is moved to a done status, or if…

To resubmit the form you would have to go into each issue and click the Reopen button and then the Submit. Once the Forms API is released (currently scheduled for Q1-Q2 2023) there might be a way to do this in bulk.

So in Insight you cannot do scope filtering, that only works when using the object on a request type. So in that case the answer would that this cannot be done, there is no support for cascading attributes in the Insight form.

You can use the Send web request action under Notifications and then use the returned result to get the name.

If you look at the To field, it states that you should enter the email address, a group or the smart value. Please note that after you entered the smart value you have to click on the gray bar underneath that says Smart value ... in order for it to work.

Hi @Scott Roehrenbeck, Welcome to Atlassian Community! You would have to use the REST API and Get project versions paginated to find the unreleased version that correspond to your search criteria, and then use that to set the fix version. JQL can search on versions, but it requires that the issue already have that version…

For now you should be able to use the lookup issues component to do this and search based on the parent link field. Once the changes that are planned to the hierarchy are in place it should be easier since you will then be able to use parent() to find all parents.

The [Short text] is coming from your query, and it indicate that it is a single line field similar to summary, and has nothing to do with the long text field in Forms. Okay, so do I understand it correctly that you are using Forms on your request form? And you have now linked the field in the form to the new Jira custom…

It is not possible to do without an app. Default JQL cannot use nested queries like that to get Epics and their associated stories/tasks/subtasks. If you do not want to use an app that extends JQL your only option is to include each Epic as part of your query.

Yes, that is possible and the field that you want to use in your JQL is request-channel-type, which can be either jira, email, portal or api.

Hi @Melissa DeLong, Welcome to Atlassian Community! Why not use the reporter field instead of a new custom field? Anyways, in order for it to work you have to feed the email address of the user to the email action, so something like this will do it as long as the custom field is a user picker field:…

Check Settings > Products > Customer access to see if you are allowing external customers or not.

You can do this by using smart values to compare when the request was created. Date and time smart values have a function for business days. So what you would do is get the created date and compare and see if it is within business hours or not, and if not send a notification to the customer.

Short answer is no, JQL does not have a function that will do that.

You would need an app in order to do that, like JQL Tricks or Scriptrunner. There are also other apps that extends JQL in the Marketplace that you can take a look at. I have used both JQL Tricks and Scriptrunner to create a filter similar to what you are looking for.

Hi @romuald tchokothe Welcome to Atlassian Community! JQL doesn't have a function that would do this for you, it is intended to search for issues, not projects. You can find project information, like the last time it was used if you go to Settings > Projects. You can also get this information via REST API and the Get…

Check your Customer permissions settings, you have to allow entering email addresses manually.

Hi @[deleted], Welcome to Atlassian Community! You should add them as Request Participants, that way they will have access to the request via the portal and will get all the customer notifications. Watchers are internal and will only allow you to add users that have Jira access.