Jack Brickey Expert

So how did the user create an issue in the portal initially? Did they log in or is a user able to create an issue in the portal without logging in. My understanding is that the only ‘anonymous’ means of creating issues is email and the embedded Widget. I use single quotes here since it really isn’t Anonymous since the…

We will need more info to assist. * check you notifications - project settings > notifications * try a mention * check your outgoing mail settings

Sure. * create a unique transition called maybe “link-done” or whatever. * Edit the transition to add post function to set the resolution to Done. * optional - Set a condition that restricts the use of the transition. * use this transition in your automation.

@priyanka.raha , please open a new thread for this question. Basically it simply comes down to how you create your filters which will be driven by your precise goals.

Do you have JSD installed? It is a separate application. Have the admin check here - Jira settings > Products

Got it. So yes I would expect it to work. I just did a quick test and it worked for me but I am on cloud. Maybe there is a server bug? I recommend the following here: * add more details: version, 2-d details (image of edit) * contact Atlassian Support to see if there is a known bug

You need to add the field to the view screen. The method depends on the variation of UI but I will assume the new issue view here. * when viewing a specific issue click on “configure” at the bottom of the right column this takes you to layout * If you see Sprint in the screen the drag to the desired area and you should be…

If you are asking how you require the reporter to specify a fix version at the Create do the following. Commentary- it strikes me odd that the reporter would specify the fix version at all much less at create but... * create a screen and include the Fix version field * edit the workflow and edit the Create transition * add…

Correct. Just because it is public doesn’t mean the user doesn’t have to login when they access the portal. While a user can open an issue via email if they wish to access the portal to open issue or view existing issue they must log in. Without this there would be no way to filter the created issue by user.

You can do this using built in automation. Something like this ... When: issue created if: createddate >= startofday(+8h) and createddate <=startofday(+24h) then: send email to reporter Otherwise... send normal notification obviously this isn’t exact and you will need to tweak to meet your needs. 

There is no “manage board”. Your image shows You do have “Board settings”.

How are you making them required? Are you sure you want them to me mandatory or are you just wanting them to be required during the Create transition?

How is this table being created? Are each of the cells, including the totals, created from a Jira filter?

I’m not following you here. You can certainly create dashboards and leverage filters that are defined by issue labels and/or date ranges. Now what you can’t do with dashboards is dynamically filter by a variable e.g. date range. For that you would need to consider using something like Microsoft PowerBI or some addon.

Hi Stuart, this helps answer your question but I thought that would add us. The default boards a Projects leverage a workflow if there’s no workflow associate project default board can’t exist. If it’s a standard classic kanban board that you create then you are always defining/associating the project when creating the…

You can create a JQL filter save it and set up a subscription to run daily and email a group of people. I’m unsure why you would want to do so for Done but nonetheless something like this... project = abc and status = Done now if you want to only show Done in the last 24h then... project =abc and status changed to…

Assuming you mean “bugs” literally, i.e. you have an Issuetype called “Bug” then.... all bugs == issuetype = bug all unresolved bugs == issuetype = bug and resolution is empty the last one assumes that you are setting the resolution field when moving issue to Done if this doesn’t get you there please provide more info…

I can't give you precise instructions as I don't have access to your instance. But basically, if you wish to have this waiting status in the other project then simply edit the workflow and add it. Now, if the two workflows are very similar except for this one missing status then you could opt to simply associate the one…

@Chris Horne, you can reach out to https://support.atlassian.com/contact/#/ and request them to upgrade you sooner.

I have not tried but I believe you can add a Validator to the transition of type field required and chose Comment as the field.

Ah ok. I think the issue is caused by the “/“ in your string. Can you remove the character and retry?

That is a different issue. You need to be sure to set the resolution when an issue is resolved. You should always do this as Jira has a number of behaviors that rely on this. Resolution can be set manually by a screen when issue is transition to any Done category status or via a post function in the workflow transitions.

I don’t understand this. I need more info.

I do not understand this screenshot as it relates to your post. can you try this query? text ~”181204893”

Go to project settings > customer permissions and tick the button for “anyone can...”

You would need an addon for such. Look at Scriptrunner, automation for jira, powerscripts, etc.

I do not use Scriptrunner so cannot provide any details of such. Based on your initial post it is unclear how it even fits in here.

Unsure. You might reach out to Atlassian Support.

Sure. You can do this one by one or you can perform a bulk update. If the later is desired do the following: * create a JQL query like this - Assignee = old-user and status != Done (tweak this to meet your needs) * click on the ellipses in the upper right and select bulk update * progress thru the screens to edit the…

You might find this article useful - configuring-jira-cloud-to-send-emails-on-behalf-of-your-domain