Comments
-
Ok, but what do you mean by "interfaces"? How sprints work with the rest of Jira? App interfaces? Interfaces to other systems? Coding externally?
-
Oh, bother, I just noticed what was in your screen-shot. You're looking at a sub-task already. That's why there's no "create sub-task" option - you're already at the sub-task layer, and you can't go any lower (sub-task of sub-task is not possible in Jira)
-
You'll need to check the docs for the app that is adding those. You've not said which app it is, so I don't know where to look.
-
No, you've misunderstood the documentation there. A database backup is no more "complete" than the xml backup. What they are saying in that doc is that a database backup is better for a large active Jira because database tools can ensure point-in-time backups which ignore changes to data while the backup is running The xml…
-
Ok, last time I put a site into Bitbucket, I did it using the command line, following https://stevegrunwell.com/blog/keeping-wordpress-under-version-control-with-git/ - the fact my git repositories are done by Bitbucket doesn't affect the underlying methods
-
Jira's default issue types were defined and built in when Jira was first written and people were mostly using it as a simple issue tracker. The default list is kept short because presenting someone with all one hundred and eleventy twelve issue types you might want to use is confusing. There's plenty of Jira uses that…
-
For Align, you'll find Atlassian will want to help you prepare for and implement Align, and they'll mostly use trained partners to provide people to do that. @Kit Friend and I were on the same partner training session...
-
What do you mean by "into"? Source control your wordpress content and/or settings? Import the site into Bitbucket's documentation functionality so you get rid of Wordpress? Something else?
-
You need to clear out the transaction log and then probably set the database into a different logging mode, or get the database owners to set up regular clearing of the transaction logs.…
-
Yes, that jump in versions is fine to do in one go.
-
You will have to ask people to find out who the site owner is. Any account with "site admin" can raise support calls with Atlassian.
-
Do you have any sub-task types enabled in the project settings?
-
None of those things exist in Jira as you have described them, and hence there are no REST APIs supporting things that are not there.
-
Server does not have team-managed projects, let alone the "features" you are looking at.
-
Atlassian.com is Atlassian's public facing website, and most people don't need access to the bits that are behind a login. I suspect you are trying to do something in the wrong place. Could you explain what you are trying to do and why you think you need to log into Atlassian.com to do it?
-
In what context? What do you mean by "interface"?
-
Yes, it will return issues where other people are watchers. The request "watcher = currentUser" is "show me the issues where I am a watcher", it asks nothing about other watchers. There is no way for a query to tell you why an issue is returned by a query, other than to include the data you are selecting on in the results…
-
Yes, you can do this, but you REALLY do not want to do it this way. The process is * Stop Jira * Take a full backup * Restore the backup to a test server to make sure it is valid * Run the SQL against the database and hope it is valid (there's more than one table you'll need to update - do you know which ones you need to…
-
This is an error on the back-end, which you (and we, the community) have no access to. You probably are not the only one getting this. The error code you have is not indicative of any specific error, it is more a marker of where Atlassian should be looking when you raise the support request. This should be raised with…
-
Ah, I see. I thought it might be this. You are (like a lot of people) assuming that Jira Server/DC and Jira Cloud are the same software. They are not. The short version of this answer is really simple - Jira Server/DC is not Cloud and it does not have that functionality (at least in this shape). You can do most of what…
-
You will need to get in touch with the administrators of that repository.
-
I'm afraid putting a word in bold while saying the same thing does not explain what it means. Please could you tell us what you mean by ""Deployments" Feature option for Jira Software Server"? I am just as stuck as @Fazila Ashraf is (probably more so), I can't think of what features you might be talking about. Could you…
-
As we can't get evaluation licences for server any more (because it is going away), you're actually a bit stuck on this one. I think all you can really do is renew your licence, then you'll be able to use the development licence to upgrade. Or, you might have to swap to a Data-Center installation and trial licence.
-
Even if you had access, mysqldump wouldn't work - they're not using mysql. The XML backup is everything you need to create a new Jira system, and has all your data. What more do you think you would get from a database dump?
-
I'd expect it to find it in the drop-down menu.
-
Create appropriate Jira projects for the calls you want to capture, and give the customers the urls to them.
-
The application logs usually catch database errors, not the application-server logs (i.e. look in Jira logs, not Tomcats). A search (case insensitive) for SQL through <Jira home>/logs/*.log should get you started
-
The export is database-agnostic, it doesn't matter what the database it came from is, or what it is going into.
-
Add "and issuetype != Epic" to your filter
-
Ok, I would separate this into two pieces, the create and the edit, simplifying each part. When you are creating issues, you do not give it an issue key, Jira creates new issues in sequence in the project they are being added to. If you are just doing edits, then you do need the issue key to tell Jira what issues to update…