Comments
-
Or status category?
-
And "simplified workflow" in Software boards gives board admins some flexibility too.
-
I did think it might well be just me who has got used to the old style we've had for years. But I've had three people new to Confluence use Cloud and turn round and say "it's unusable, you mentioned other non-Cloud options?"
-
Depending on your startup system, the installers do not always enable them for startup. What Linux do you have? Or more importantly, what's the start system? Systemd, Upstart, SysVinit etc? (Try, as root, running systemctl - if you have that, you're on systemd)
-
You can upgrade to any version of Jira released before the end of your licence. Imagine the release schedule is: * 7.9 - current * 7.10 - released 9th June 2018 * 7.11 - released 11th June 2018 You can upgrade to 7.9 now or any time in the future. Same for 7.10, even after the 10th, you could go to 7.10 in 2020 if you felt…
-
There is no route to downgrade a Jira system. There are some workarounds - rarely, the database is compatible enough that you can just change the version flag and it will work. A little bit more likely is you can export to xml, hack the flag in there and re-import. But I doubt these will work at all for versions between…
-
No. Confluence has a tiered licence model for number of available users. If you have 250 licences, then you can have up to 250 accounts enabled for access. If you go over that, then Confluence effectively becomes read-only until you reduce the count, or apply a licence for the next tier up. With your 270 users, they only…
-
The last line about the licence is just saying you have an evaluation, it is not an error. I think you've got a blank screen there because there are no projects in Mantis available to import. It's trying to ask which one, but there's none available so you get an empty box.
-
An evaluation licence simply stops working at the end (system goes read-only). It has no effect on functionality. Could you explain what happens? Your question is very unclear on what you are doing, and what you are seeing from the point of "complete all fields and ..."
-
Running as jira1 is fine, it just means the installer detected a user called jira already and didn't re-use it (because it may be from a failed or removed previous install, or have been created differently, and it doesn't know if it's suitable) The creation of a symbolic link is normal, it's systemd creating the startup…
-
Are your source and target Confluence systems both the same version? This sort of error occurs most frequently when they're different.
-
An issue collector would bypass the usage of a form in Confluence, as it has its own fields to pass to Jira, unrelated to the content of the Confluence page. It is a very good idea, if you can get all the fields in there in a way that visually works for your users, and it requires no coding beyond a copy and paste into…
-
Sorry, but I don't understand the context of "prefilled" on a view screen. There's either data in a field or there is not, and it doesn't change on view.
-
I think I'll go for a Waendal Walk instead of watching.
-
Yep, understood. You will need to get a forms add-on for Confluence (it's a wiki, not a form system), and then do a bit of coding to get the submit to poke an issue into Jira over REST.
-
I'd use ScriptRunner (I am, of course, biased there, as I work for Adaptavist. I try not to plug us too much, hence the slightly neutral answer above. There are other options, just not ones I'd choose when I have SR available)
-
There are several ways to do it, but they all boil down to "something has to tell Jira you are working on something". How does phpStorm know you are working on something, and does it have ways to make remote calls to Jira to tell it?
-
It all depends on what you are doing to "collecting a request via form". The obvious options is to have the user creating the form click "create issue" in Jira and have all the form data in there. This is also the easiest, as it means no coding, no fuss and you have all the fields in Jira already for the lifecycle of the…
-
Not with ScriptRunner (or the other add-ons that do scripted fields). The point of these fields is that they are derived from rules you set in their code, and not enter-able because they're calculated. But you don't need an edit-able scripted field. Just create a field that takes its output from A if A exists and B if it…
-
You can just delete a workflow (if it's not used) and it won't touch your status The status is linked to the workflow, not part of it, and the delete does not want to touch things that might be used by others. It's annoying that the import doesn't see it that way.
-
No. You need an add-on that can provide a function to pull the data from the history, or catch and record it at the time the transition is executed.
-
Ah, hang on, this is Cloud isn't it? Extended permissions are not available on Cloud (yet).
-
You can download a backup of everything from Admin -> Backup. The backup is suitable for import into a Server version of Jira (which doesn't have the new layout)
-
Ok, that rules out a couple more things (actually quite a lot). But I could still use a look at a single issue's status and status category.
-
I get the same as you, with Story Points. No customisation.
-
No, because status is an indicator of position in a workflow, not an action. Post-functions run on actions. But the "All ->" transition is still a transition. You can add post-functions to them, like any other transition.
-
This sounds like you have set up one of two things: A board filter that excludes issues in certain status Column mappings on the board that are not mapping the missing status If you're not sure, could you show us the filter on the board and the board mappings?
-
You need to explain what an ATG Core Test Case is and how you've connected them to Jira
-
We don't know. We're a community of end users. We can't identify which one of hundreds of thousands of Jiras might be yours from your question.
-
There are a lot of Jira systems out there, and we're end-users, like you, of many of them. We don't know which one you might be talking about, but it sounds like you need to get in touch with the administrators for that Jira, and ask them.