Comments
-
You will need one of your site administrators to add your account to the list of site admins.
-
No, it's just totally different to a field.
-
Your digging served you well - Next-gen projects do not yet support sub-tasks
-
What you're describing is what I would expect to see if one of your admins renamed a priority. The name is a display label, not the actual value, hence there's no changes in the issue history. If you have admin auditing enabled, the rename should show in there, along with who did it, but if it was not enabled when the…
-
Could you explain what this has to do with Atlassian stuff?
-
I can't do anything about verifications - we're a community of end users who try to help each other, not Atlassian themselves (although you can find them here). Your user will need to contact them directly to chase it up! I would go via https://support.atlassian.com/contact
-
You can add new types of project, but only by writing an App that provides the new type. This is not a trivial thing to do - you'll have to code for all the different things your new type might do differently to the current three types. Most people who think they want to add a new project type usually mean something less:…
-
https://support.atlassian.com/contact is the way to go, I'd suggest looking for the "documentation is incorrect/missing" route
-
Status is not a field, it's an indicator of where an issue is in the workflow. To change it, you have to go through a transition. In Cloud, in the next-gen view, the transitions are represented as a drop-down, which feels like it's an "edit of a field", but that is not going to be implemented in the classic projects or go…
-
Archiving is in Jira 7.10 and above, but data centre only, I don't think Atlassian plan to bring it to server. I suspect the thinking is that if you're big enough to be thinking of archiving, you probably should be on Data Centre anyway
-
What do you mean by "add a new Jira instance to same domain"? If you have a jira running on <something>.atlassian.net and you want a second instance, it won't be on the same domain, it will be created on <something else>.atlassian.net. If you use different Atlassian accounts to buy each system they will be billed…
-
Hmm. I don't have to do that on the Jira side when I've migrated a server from one place to another, although quite often the other end needs re-authentication because the connection is coming from a new place. The data in the application links does not change when this is done though.
-
Start at https://developer.atlassian.com/cloud/jira/platform/rest/v3/ and check the authorisation and security links there
-
Start at https://developer.atlassian.com/server/bitbucket/how-tos/beginner-guide-to-bitbucket-server-plugin-development/ if you want a proper app to do it in the UI.
-
You'll probably need to explain what "ASPICE" is for most of us. (The short answer is "yes, if configured suitably" though)
-
You had not mentioned what you were doing at all - in your question, there was no mention of any Atlassian system or what you were backing up. Could you explain which "system tools" you are using? Atlassian recommend database "system tools" for backups, but there are two types of export/backup also inside Confluence that…
-
The system does not capture and store that information. You'll need to write code to catch it, store it, and report on it.
-
I don't quite understand why you don't log in as the admin user you have to set up when you run the install of the software. But as we are a bit stuck, going to Atlassian support is the right thing!
-
Could you explain what this has to do with Confluence?
-
No, they can't support a system where the end-user might be able to completely break everything by having access to the back end. It defeats the point of SAAS offerings!
-
You do not. Cloud does not allow any access to the database.
-
As you go through the install, it asks you to create an admin account - you should be able to use that to log in, then you can create more accounts. There is no "admin mode" or "admin login" - you log in as a user who has admin rights on their accounts and get the admin options offered.
-
You say that the application links are not replicated - could you explain what you are doing that removes them? When I copy Atlassian systems across servers, things like application links are kept, so I'm wondering what you're doing to lose them.
-
You can limit the components to a list by having the project admins define the components correctly (non admins can't edit the list) To limit it to one, find the .vm file that defines the field layout on edit and change it so it only allows for one selection, then restart Jira. From memory, it's component-edit.vm somewhere…
-
You should log in as an admin. The admin account was created during the installation, try the username and password you gave that account.
-
This is something that needs to go to atlassian support - raise it at https://support.atlassian.com/contact
-
There is currently no way to do this. It's one application with one base url.
-
It should be interpreted as "respondents have a lot of things coming in and sometimes miss replies" The problem here is that the customers have been configured to be able to see other organisation activities and are allowed in to all of the portals. Limiting them with the service desk project permissions will solve the…
-
@Tom Synnott- sounds like a custom field to me.
-
This is all about what you mean by "track". All the changes you list (and more) are listed in the issue history (by design - the issue history is the main reason Jira exists!). So the answer to your question on the basic level is "look at the issue". I suspect you mean you want something more complex than that though, so…