Nic Brough -Adaptavist- Expert

Welcome to the Community! You say "The fields are connected. In our classification this is working, but when I try to create a scheduled issue this fields are here without matches.", but I do not understand what it means. How are the fields "connected"? (Other than being on the same issue). What is a scheduled issue? How…

Elastic is the search system underneath bitbucket. The file you're looking at holds keys for encrypted access. The errors you are getting are happening because your server is not set up correctly. The Linux user running the service does not have the right permissions. This usually happens when someone starts the service…

Could you explain what this has to do with Confluence?

What errors are you getting when "it is getting failed" and exactly how are you trying to deploy it?

Just so you can tell others that @Brant Schroeder is spot-on if they ask for more tech detail: A Jira index is a pile of local files Jira generates from the database. They help it do most of its day-to-day work a lot faster than if it had to read the database for everything. The reindex function rebuilds a clean index from…

No, that's not right, you have gone down into it too far. It is a lot more simple. * If issue reporter is part of security scheme, they can see the issue * If issue reporter is not part of security scheme, they can not see the issue That's it. It really is that simple. The ability to set a scheme doesn't matter.

I am sorry, but I do not understand the question. You say >I need a simple read only field >... > and added a default value as Defect . But when I open the Transition, the field is blank , it is not showing the default value Why would a read-only field have a default value? By definition, a read-only field cannot be given…

You do not hide them, the comments are an important part of what an issue is for. If you genuinely are not going to use them, turn them off, in the permission scheme.

You would need to copy the key into an editable field that you can present to your users, and then probably destroy what they enter into it. Could you explain what use this would be to the end-user? What does showing them a key they don't care about improve their usage or reduce their load?

This is a warning for developers, not a "problem". Could you explain what the actual problem is, and why you are looking at a snippet of log that is almost certainly unrelated?

If you read an issue over the REST API, you can get its full history, which includes a date and time of every change of status (and create as well, of course), so you can easily code something to parse the history for each "changed status to" line.

Welcome to the Community! What do you want from this "integration"?

Again, comments are not a field, and they are not being displayed in the tabs, they are being displayed in their own section on the page.

Welcome to the Atlassian Community! I'm afraid you are probably in the wrong place. instant27001 is not an Atlassian product as far as I can tell, so I doubt anyone here will know much about it. My guess is that they use Atlassian's Confluence for their documentation and you've clicked on "help with the docs system"…

Welcome to the Community! No, it doesn't make any sense for a Jira issue to have an email address. What use would it be? Do you really want to have to build mail services that can handle 12 million individual email addresses for issues in an issue tracker? (I picked 12 million because that's the largest Jira I've worked on…

You already asked this - see https://community.atlassian.com/t5/Jira-Software-questions/I-get-the-error-There-are-no-issue-types-with-compatible-field/qaq-p/1833004

I'm sorry, I don't understand the question, or what you think the problem is. If you use issue security to hide an issue from someone, they can't see the issue. Other issues have nothing to do with it.

It's the system that goes read-only. Cloud is different though, this doesn't apply here.

Welcome to the Community! https://library.adaptavist.com/search?page=1&products=jira&platforms=cloud might give you some hints and samples to get started with.

Yes, but you need to do it with structure, it's not a "can (not) see page". First, you need to ensure that the freelancers all have view rights for the space. All of it. That's the easy bit. The second, more complicated bit, is that you now need to split your space into two (or more) parts. This is because page view…

>I am told that Confluence/Atlassian manages Confluence for the company. I suspect that means you are on Cloud - this means they are providing the service, but they are not your Confluence administrators. Atlassian don't do administration that you can do for yourself. You'll need to talk to your admins about getting the…

Look for the "conditions" in these guides - a condition on a transition hides the transition from people, by removing the buttons from their view.

Welcome to the Community! Jira takes a couple of minutes to get going, but will show as a running process as soon as the startup script finishes. The output you've got from the startup script is only from that script, it's not the application log, and it's the application log you'll need to look at. Have a look in <Jira…

You can't swap types - it would need to provoke an entire "move" process for all the affected issues, which is slow and painful - you'd need to identify a new parent for every issue currently of that type at the very least! There is a very simple fix though. Rename the current "sub-task" to something else. Anything will do…

There is a lot in there, so I may be missing something, but I am not seeing a problem with this. I'd like to paraphrase your question to check that I understand what you are seeing. Let's say we have two users with access to the project, you and me. Your single management security level has a rule that says "Gautham can…

No, you can not. See my previous answer.

Stop reading the database, it's not designed for reporting, it's complicated, messy, and not structured in the way you are guessing it is.

I've had the most success with issue synchronisation at scale with Backbone - maybe you should look into fixing the problems you're having with that. If you're determined to change though, then the one that is only very slightly lower on the list is definitely Exalate. I only recommend Backbone over Exalate because I've…

No, this is nonsense. The issue id is unique and immutable (the issue key is not), but the workflow transition ids are not. The transition Open -> in progress can have a different id in different workflows, and you will find different transitions in different workflows have the same id. And they can change as people change…

Ok, you'll need to read the logs for group related errors. See <jira home>/logs/atlassian-jira.log