Comments
-
You can order by any field you want in a board, but the moving of issues around in that order is only possible if the ordering is by rank. This is not a limitation in the software, it's an informational one - the rank represents the order you have put things in (or let them drop into it). Imagine a worked example, where we…
-
Probably not actually. There are no prerequisites for Scriptrunner, other than a Jira (or Confluence, Bitbucket or Bamboo to install it on). Even if you were able to enable the module, there's no point - you haven't got Automation, so it wouldn't actually do anything. I think I need to ask what you're trying to achieve…
-
"A physical % complete" is not any more descriptive than just "a %". What are you measuring for completion?
-
I suggest you re-read the conversation again. You've missed the parts where the requirement is found to be ill-defined (because it's a guess based on experience of totally different software which is built differently), and, when explored, it's already met, just not the way the guess at a requirement was made.
-
Those two modules require that you have other apps installed, they can't be enabled unless you've got the apps. I'm not sure about the macro metadata provider (possibly something to do with a graphing or diagramming app), but the Automation error suggests you don't have Automation installed.
-
One of the things Cloud is for is staying on the latest release of the service software. It's not their fault if they make a change that breaks an unsupported browser, you should be keeping up with the browser software.
-
So you're not using a supported browser. Your only option for a fix here is to use a supported (or at least working) browser. Atlassian are not going to change anything to support a non-supported browser.
-
Are you using a supported browser?
-
Could you tell us what the errors and symptoms are please? "Confluence not opening" does not tell us anything about what is wrong. However, even if you do have a useful message or pattern of failure that can get us started on a fix, I'm afraid the answer is likely to be "you need to fix your side". Atlassian Cloud is…
-
You can safely change the names of the levels any time, so I wouldn't be too worried about how much they are used. On the other hand, rationalisation and standardisation - always good, and you need to know current usage before you can come up with a better scheme! This does assume that you, as an admin, are included in…
-
What is this "vendors list"? Where are you seeing it?
-
This is counter-intuitive I think and not explained well in the docs, but Issues are not the same thing as Requests. A request is a wrapper around an issue, for the benefit of the customers - customers only see requests, but Agents get to see both the request and the issue behind it. These two artifacts both have workflow…
-
Why are you restricting knowledge base articles? That defeats the point of them!
-
I've always had "fun" finding dead projects, to the point where I created a project report for admins as one of my earliest plugins (for version 3.0.3 of Jira, to show my age!) One thing to remember about doing it this way is consistency. If you are logged in as an admin, and you use the administrators project list, you…
-
I am a little stuck on what problem you are trying to solve here. If I understand it right, your agents are sending knowledge-base articles to customers? That should be fine, as long as the articles are in the knowledge base spaces, they won't be restricted away from the customers. If your agents are sending pages from…
-
Ok, this is a merge then. You'll need to get extracts of what you want to merge into the target system in a format that the importer code in each system can read.
-
All of these since my last comment are symptoms of you using the field for the wrong thing. Stop looking at creator and look at reporter for this data. Use reporter and creator properly for the reasons they were created.
-
If you set up the permissions to work like that, yes.
-
The increment function cannot read strings and guess that they might be numbers. You'll need to code something that converts to a number, adds something to it, then converts it back to a string. I do not believe automation can do that. You'll need something like Scriptrunner, or change to using a numeric field (then the…
-
The Atlassian answer is going to be Jira Align or for smaller teams who won't be doing the higher leves, Advanced Roadmaps
-
Your JQL is looking for "date larger than or equal to 365 days ago", it's not looking at calendar years. You should look to the calendar functions, start of/end of, day, week, month and year. For this one, I think I'd use created > startOfYear() (If you wanted to include last year, you'd use "created > startOfYear(-1)" )
-
I think you've said "achieve" when you mean "archive". The free plan does not enable project archiving, that's why you don't have permission.
-
You can not search for what is not there. The best you can do is infer (work out) the list of empty projects from the results of searches for non-empty project. Create a search for all issues (essentially, no JQL at all!) and save it. Go to a dashboard and add a "filter statistics" gadget, selecting "project" as the…
-
You don't, as discussed above. Changing the default sort order of comments does not require reindexing anyway.
-
Yes, they can, but they'll need to know the name of the other user, as they'll have to type it in full to get it selected.
-
Do you mean you are trying to migrate a Jira, Bitbucket and Confluence set from one instance to another? Or you are trying to migrate some stuff from "iotfynow" into an existing Jira, Confluence and Bitbucket stack?
-
This is what says - the Jira server is trying to ask the email server for emails to read and convert to issues or comments, and the email server is not responding to it at all. Either * the email server is not running at the location given * your network is not letting your Jira to talk to the email server * your email…
-
There's no need for another tool, you just need to correct your definition of done. Two boards is probably the answer for you here. You won't have the "issues automatically closed" problem if you define the boards differently. The development board needs to have a last column that means "done for the team that the board…
-
You need to start with a clean (meaning empty) database. You can't point a half-setup installation at an existing data set, it cannot know what to do with it.
-
As usual with video instructions, it's out of date. Atlassian abandoned the poor design on the left sidebar a while ago, and moved back to a menu across the top which actually works.