Comments
-
I'm not sure how to do it with either of those, I rarely use them. I suspect it should be possible, but I've not tried.
-
No, because a done issue should not be in the backlog. It's finished with, and a backlog is a list of outstanding work.
-
I'm afraid you can't yet do that. Done = last column.
-
That is odd! But yes, sounds like a bug in Word!
-
That's not the right approach. The issues are done, so they should not be in the backlog, as they're just noise. If you want to re-link them to different epics, search for them and use bulk-edit to set a new epic-link. (Not that there is usually a lot of point, as they're done)
-
Ok, I think it might be converting with the wrong variable types. Could you try these two lines as calculations and see what they do (on any issue that has a number in the seconds field) return (issue.get("customfield_13315")); return (issue.get("customfield_13315"))/1; I know a divide by 1 looks a bit odd, but it's a test…
-
Looking at the two issues you have in your question * Where does the "project category" appear on the screen when you look at JCF-2877? (If it appears at all?) * Is there a custom field in your installation called "project category"? * What is the difference between the two issue types? Look especially at the issue screen…
-
Because 7.6 is the enterprise release, so it's going to get updates at that version for a long time. If you encounter problems in 7.12.3, and Atlassian fix them, they will go into 7.12.4 or later and you'll need to upgrade to get them.
-
You'll need to find a scripting or automation App that can support calculating one field from others. I'd use Scriptrunner of course (as I work for the vendor, I've got expert scripters on tap), but have a look at the automation and other scripting Apps too.
-
Yes, that's correct, there is no version 7.11.3. Whomever wrote that notice for you is not up-to-date with what is available. All you can do is report their error back to them and get confirmation on whether they mean to move you to 7.12.x or not.
-
All of them. Atlassian do not put "unstable" releases into the download list (they do release "early access", which you could call "unstable", but these are held separately). I would tend not to go for a release with a .0 on the end because these are new to market and Atlassian can't test every possible combination that's…
-
Does SUSE support running the version of Java your choice of Bitbucket version? If so, then yes, Bitbucket is compatible with it.
-
Remaining time on an issue is not a custom field, so I suspect your "get" commands are not getting the right thing. Unless you have defined a custom field for it, in which case, start with a look at the type of field it is. Numeric? Holds number of days, hours or minutes?
-
Best you can do without a plugin is to embed a link in the field description that points to a document that tells your users which one is which.
-
Service Desk attachments are stored as part of the Jira Issue that is behind the SD request, so they're in the same place as your non-service-desk issue attachments. This is <jira-home>/attachments (check the system info to see where <jira home> is if you don't know). Jira always tries to use that directory, no matter…
-
There are limits - the disk space for smaller systems is limited to 25Gb (including the installation, database and attachments), and then 100Gb for larger ones. If you go over that, then Atlassian will start talking to you about how to reduce it or move up to more storage. Most people won't and when they do it's usually…
-
Those errors are from the browser console, we need to see the error you get on the front end. Although I would try clearing the browser cache and restarting it - ns_error_file usually refers to damaged files on the client side, not the server.
-
Could you explain what you are doing a little more? Why are you using SOAPUI when SOAP was removed from Jira? What is making the call to the scripts that are on the aid-frontend site?
-
That's good detective work - it means the network is probably fine, and the problem is what how the browser is working with what the server is handing it. I'd want a look at the html the browser thinks it is getting and any warnings or errors - check the developer tools in the broken browser to see if there is anything…
-
Not if they are on Cloud, the licences are not handled in the UI.
-
I'd expect the screen to appear on the "All" -> "Done" transition you have in there.
-
When you look at the list of attachments on a page, you have several links to them exposed. Most of the links are specific for a version of an attachment, but one of them is a more simple link to "latest" If, for example, we have two versions of a file and we expand it for the versions, we get a display like: * File.doc*…
-
Edit the workflow and look at the transitions that take an issue from one status to another - use the "columns" tab in the board setting to see where each status is in the board and hence which transition takes an issue from one column to another. When you've identified the transition you need, look at the "conditions" tab…
-
You are using a Cloud system here. They do not have licences for Jira (Core, Software, Service Desk) or Confluence etc, it's done behind the scenes in your Cloud account.
-
I'm afraid not, Jira does not have that level of granularity in the project admin permissions. A project admin gets access to users, versions and components, plus the new project settings if you allow that in the project
-
Make sure you do not put the whole home directory on a shared location - the index and caching will fail if you do that, they must be on a local non-shared disk.
-
The server needs read/write access to its database. They won't start up without read-write access. So, yes, to test this for DR, you will need to stop replication, make the replicated database read/write and then start the DR nodes.
-
Jira doesn't have any support for moving fields around like that. You'd have to take apart the code that renders the screens and re-code them to allow for it.
-
You'll need to find or write a new field type to do that, Jira's cascading select is just two options, not users or projects.
-
The libraries and structure of javascript being loaded in Confluence and Jira often changes with a new release. You will need to re-write your javasscript to fit with the new systems.