Boris Berenberg - Atlas Authority Expert

Here's an example that is close to what you need https://community.atlassian.com/t5/Jira-questions/script-validator-check-dates/qaq-p/400542

Can you describe what you hope to get? You could do something like: PROJECT = ABC ORDER BY COMPONENT and then export to Excel CSV within the the Issue Navigator

You now need to go to Manage Filters -> Edit Filter Details

You could do a validator using a scripting app such as ScriptRunner or PowerScripts

Not possible without a third party app. 

If you look at the Dataplane historical versions, they have old ones that support 6.3 https://marketplace.atlassian.com/plugins/com.arsenalesystems.dataplane/versions

Actually you're totally right, my bad, it can only show you issue count. So I would amend my answer to say, JQL based reporting will always return issue count. If you want to perform operations on field values you will either need to do something like Scriptrunner where you embed the results into another ticket, or a BI…

Take a look at EazyBi or Dataplane. Both are great tools and have older versions that should support an old version of Jira like 6.3

I believe that the responses are used to improve the search, but are not visible to you as an admin. 

https://docs.atlassian.com/confluence/latest-server/ You may also want to look at https://community.developer.atlassian.com/ and https://developer.atlassian.com/confdev/confluence-plugin-guide/writing-confluence-plugins

Try using the Two Dimensional Filter gadget. I believe that can sum it up for you.

Probably better suited for https://community.developer.atlassian.com/

You will likely need to have an Atlassian step in to help. If you're on a more than 10 user license then you should file a support ticket. Otherwise let me know and I'll see if I can get you some help.

That is done using a third party app https://marketplace.atlassian.com/plugins/com.capitaladdons.confluence.plugin.macro.ca-jira-confluence-issue-macro/server/overview Do you have that installed?

You could create a cyclical transition which adds a watcher, then have automation fire the transition. To do the actual bit with adding the watcher, you will need to use one of a few more complicated techniques, take a look at https://jira.atlassian.com/browse/JRASERVER-43158 for more information.

You can likely file a support ticket and request they open a bug on this? Can't hurt.

Can you share your updated connectors and proxy config?

As I said, you missed all the proxy parms in the server.xml file. Re-read the Tomcat portion of https://confluence.atlassian.com/adminjiraserver073/integrating-jira-with-apache-using-ssl-861253896.html and set the proxyPort, proxyName, and scheme parameters.

I would confirm that you properly set your proxy settings in the server.xml file, and updated the base URL in Jira.

You have to be a Jira system admin, not a project admin. Reach out to your admin team and request they add the issue types you want.

That error doesn't really show us much. I would suggest you look at the atlassian-confluence.log file in the Confluence Home directory on the filesystem. That will likely have more information for you. I am not sure what updating Jira has to do with Confluence though.

You may have more luck at https://community.developer.atlassian.com

My guess is that this is occurring because the product is currently undergoing a transition in both the design, and the tooling (ADG3, AUI, AtlasKit). Unlike many other companies that would roll out a design change all at once, Atlassian seems to be doing this in chunks.

It looks like the content is correct? Though I don't speak Japanese. @[deleted] maybe you can help here?

I emailed an Atlassian I know, hopefully they may be able to help you out.

I just got back from Germany and spent a week in Berlin, wish I knew your team was there before.

Hmm, sorry but I am a bit stuck without digging further into your system. I would consider reaching out to Atlassian support directly.

Nope, I just moved this question into the right category, no need for you to do anything. I don't believe there is any way to change the behavior you are describing. You can add a comment to the appropriate ticket where you agree:…

This is actually not possible out of the box: https://jira.atlassian.com/browse/JRASERVER-1676 Are you using Tempo or another app which provides this functionality?

Are you sure you meant Confluence when creating this? It seems more like a Jira question.