Jack Brickey Expert

That means that you are on a free/ starter license. As such you are limited to the Community for any support. Unfortunately the Community is unable to help you in changing the site URL since we don’t have access to your instance. Unless you upgrade to Standard you are stuck with the current URL.

You will need to reach out to support for this - https://support.atlassian.com/contact/#/ 

The developer site is down as identified here - https://developer.status.atlassian.com/ best to monitor things there

I would use Automation for Jira for this. Now as you are on cloud it is important to know that, as a result of Atlassian’s acquisition of the vendor of this addon, the software is being integrated into Jira natively and is due to be rolled out this quarter I think. As part of this process, that addon has been removed from…

If you are asking whether you can use the “start release” date within a query/gadget the answer is no. That field is not available. That said you could create a new custom field, set it as appropriate and the use it in your queries and gadget.

That is saying that your current board includes more than one Issuetype (common) and those types include multiple workflows. As such you can’t convert to simplified like that. I’m not sure the best way to do so TBH as I have not attempted. My thoughts would be to associate all issuetypes to a single workflow and reattempt.

Backlogs are not associated with Projects really. Rather they are associated to Boards. Are you wanting to have multiple boards but one backlog or one board and on backlog? The later is easy the former requires a bit of diligence by the team as you would have individual team boards and then you would have one board for all…

Can you share a screenshot (full) of where you are attempting? Also, just curious of your use case. Do you link an epic to an epic?

Not “in” the project but you could opt to create Kanban/scrum boards and locate them under your profile while associating with the NG project.

You can create a next-gen issue just like you do for classic. You can do so on the board or using the “+” in the sidebar. Now if you don’t see a “bug” Issuetype then you must first add the type under project settings.

Disclaimer: I have not done this to confirm it works but here is what I would try first. option 1 - transition post function the idea is to use a transition post function to copy the request date into the created date. Here are the steps: * edit the associated workflow * add a ‘reentrant’ transition (exits and renters same…

@Mark Crocker , I’m not sure I am following you here. This thread is about changing the appearance order of priorities. Which can be done as described. Ranking within a board is not directly associated to priorities. Sure you could rank issues (Classic only) by priority simply by dragging them around but that would be…

I was like .... and then I was like ....

you might find this thread useful - Stop-sprints-from-other-projects-displaying 

that sounds really odd to be sure. I'm not sure I have any ideas of what to look at. What if anything has changed? Any smoking-gun that would lend a clue as to the cause? Do you have any addons? I would certainly suspect something there as a potential culprit. Ultimately, you may need to reach out to Atlassian Support so…

Hi @Logan2050Stark , that can be a pretty big topic especially when you consider classic vs. next-gen projects. Here is a place to start - managing-users-and-groups . If you have some specific questions LMK.

Alternatively you could use something like... ...and fixversion is not empty and resolution = Done... obviously either solution requires diligence. 

Unfortunately you cannot query on “released”. What you could do is to create a new custom field “released” and set that on all issues when released and then set a condition on that field.

Not OOTB. You might consider Scriptrunner which has a function issuehaslinks which will allow you to find any issue have or do not have links.

You can set up automation to notify an individual when customer comments. However, consider maybe having an Escalate transition. Instruct the customer to use it if required. Have automation trigger on the transition to notify the appropriate person.

Hi Brad, I have seen this but don’t know much about it TBH. I suspect it is performance related but I don’t know the rules that are being used to define what is displayed. I really haven’t seen it impact my boards and I don’t seem to miss anything except in Done column.

i'm wondering if there is some cloud issue causing this. I am not experiencing any issue AFAIK. If you think there is an issue please contact Atlassian Support.

you can't group them under one "Status" as they are separate statuses. However, you can certainly create a filter that results in all issues in multiple statuses. You might even consider using the following.... statusCategory != Done that would give you every status except those that are in the Done status category. if you…

I see. You might review this article - set-up-an-open-portal however, it doesn't discuss viewing existing requests. Again, I'm unsure how it would work to prevent others from seeing all requests w/o logging in.

I am not familiar with that gadget. It isn’t part of my default gadgets. I am guessing it is an addon. If so I would reach out to the vendor support.

Sure this is typically done. Project settings > notifications > Create. Be sure that those you want to be notified are listed there in a role/group.

So you want to restrict agents from public comments but they can work issues? I don’t know of an addon. One possible hack (?) is to have two levels of agents, which you do, but create a separate project for the non-public team and created linked issues between the public project and private ticket.

Depending on how you want to present the data you may wish to look at the two dimensional gadget or possibly a pie chart. 

If you want them to only make internal comments and not public then they should not be agents for the project. As an agent they have the ability to make public or internal comments

The best way to do this is to leverage the resolution field. However, this assumes that you always set the resolution when moving an issue into any Done Category status. JQL - resolution is empty if the above resolution assumption is invalid then you will need to do something like below and specify every Done status... JQL…