Boris Berenberg - Atlas Authority Expert

My guess is that type was the original and a lot of people didn't understand it so Issuetype was added to make things clearer, and type was left for legacy reasons. However, this is just a guess and I have no evidence to support this. In your situation, the best thing I can suggest is to move away from the Type…

You could use the Automation add-on to transition the issue back into the approval status if it is in a status after approval but hasn't been in the manager approval needed status.

I would create a space they all have access to. Then create sub pages for each user, and restrict it so only you and them can see it. Then create a Template for the space that they can all use for reports.

The only way I can think of doing this would be with a custom add-on. Seems a bit complicated, any particular reason why you would wanrt to do this? It would break all existing filters where type is used.

Looks like nope: https://twitter.com/JIRA/status/905486179901906944

As in days from when ticket was created to when it was closed?

Make sure that you also share the filters that power all the gadgets.

It's solvable but in a different way. Create a field on Issue B to track when Issue A is done. Change the workflow for Issue A to set the value in Issue B using update linked issue post function. Then just query for issue B and field value.

Well your example JQL above didn't make sense because it doesn't show any kind of an attempt at a join. Explain further what you're trying to do and we can try and help.

Is it only cloning? Is creating also slow? I don't think we're going to be able to troubleshoot this kind of thing in this kind of forum. I would urge you to contact your admins (if you are not the admin) and reach out to Atlassian or a Partner to troubleshoot.

It says to create a support ticket. Did you try doing that? Only Atlassian staff have access to those systems.

Yes this will work. I would suggest moving / renaming the dirs, not overwriting them. 

I don't think you can, but isn't that in the title?

The best suggestion I can give you is to remove the field from the edit screen. Create a transition with a screen that has only this field. Set a condition on the transition that it is only there when the field is empty.

How do you define work done? Hours of work? Story points? Number of issues?

You can just have a transition from Any to Done with a post function to set resolution as Invalid https://confluence.atlassian.com/jirakb/resolutions-are-not-set-225122076.html

Depending on when you installed it there may have been something funny with the licensing system. While waiting for better answers, I would suggest you completely uninstall and re-install the add-on to see if it helps.

The short answer is no. In SQL terms you would need a JOIN, in JQL there is no equivelent. You may be able to get it using an add-on. Are you on server of cloud?

The transiton is called a Step and connects two Statuses. The Step name, and the Status name are often the same. They don't have to be. If they are not, then the buttons will show the Step names, and the Status field will display the Status in which the issue currently stands.

At the end of the day, no macro can modify whats going on in the editor. The closest I can say is you could have a macro that displayed the character count, and try and detect if it's being used in a preview view, and then have text entered into a property instead of macro body. If you don't detect preview view, you just…

https://confluence.atlassian.com/doc/content-by-label-macro-145566.html https://marketplace.atlassian.com/plugins/net.customware.confluence.plugin.reporting/server/overview But this question was more focused on JIRA I believe.

Did you update the baseurl? https://confluence.atlassian.com/doc/configuring-the-server-base-url-148592.html

Hmm, not sure then, Zephyr shouldn't be modifying the colors of anything in Service Desk. If you really think that is the case, work with your admin (or do it yourself if you are the admin) to disable Zephyr for a couple of minutes outside of normal business hours to verify.

https://confluence.atlassian.com/adminjiracloud/importing-data-from-github-800860703.html

Importing a new document would overwrite the entire old one. So it makes sense that the anchors no longer work. What are you importing from? Try adding the anchors into the source document.

https://confluence.atlassian.com/adminjiraserver072/integrating-jira-with-apache-using-ssl-828788158.html https://confluence.atlassian.com/jirakb/integrating-jira-with-nginx-426115340.html

I am assuming that you are on Cloud and am guessing that you have been enrolled into an experiment. Try opening a support ticket and asking if that is the case, and if so, if you can be removed from it.

Take a look at https://confluence.atlassian.com/confkb/how-to-embed-smartsheets-in-confluence-using-the-html-macro-800862394.html

keyboard shortcuts are another thing that trips people up sometimes

Are you currently using a Cloud instance or a Server instance? If Cloud, then it is not possible. If it is Server then you can host the application at any URL you choose. Typically it is recommended that you use a reverse proxy such as Apache or Nginx to perform SSL termination.