Comments
-
Yes, in order to change status, you have to use a transition. The transition therefore must exist for you to trigger it! So, you'll need to add a transition from the current issue status into the "Scheduled" status.
-
Possibly. It depends on your processes and how your people want to work together. Most important is your desired process, not "doing it the right way", but "doing it the right way for you" Take a look at the life-cycle of a typical one of your stories, and what it usually should go through. Is it reasonable to expect that…
-
Yes, and you've almost answered your own question - NOT is a valid operator in JQL. Most of us would use the ! shorthand though. Assignee is not currentUser() Assignee != currentUser() Both do the same job.
-
Yes, I've run it behind several types of security systems. You usually need to think about their configuration, so that they let through what you need. (JQL can look a bit SQL-like for example, and you'll need to ensure all the web and REST urls are passed through ok)
-
Odd, I assume it's got a Cloud version? That should show when you use the "find new app" function. What do you see in there?
-
On Server, it will be at the top right, near the profile and help icons. On Cloud, it's in the second-left panel, near or at the bottom of the list of options (depends on whether you're in a project or not as to where it is and whether you are offered project-admin or jira-admin).
-
Yes, "empty" does mean a new installation. If you want it on the same machine with the same settings as the old one, you will need to uninstall it. Also you'll need to clear out the database it is using. The licences are done by keys - you can paste those keys into the new installation, no new purchase or rebuilding needed.
-
In your screenshot, you have some options on the left. If you just want a child-page display for the current page the macro is on, leave the "parent page" empty. If you want to show the child pages for a different page, fill it in with the location of the page you want to set (This is usually "<space>:page name", with…
-
You need to make someone else the billing and technical contact before you delete yourself.
-
It's to the right of the page when you go to Admin -> Manage add-ons. That assumes you are on server. If you are on Cloud, you can't upload add-ons, you have to "install" them, which is more a pointer to some connector information than an install. .obr and .jar type add-ons can't be added to Cloud.
-
Why is it a strange argument? The drop-down, in my experience, leads to poor data quality. That's a poor choice made by Atlassian, not me, and I have already seen it lead to problems, with two clients suddenly asking how they can fix the 20% of their issues that are in the wrong status (previously around 1%). But given…
-
There's more than one app that can use that notation. Could you tell us which one you are using?
-
issue.getProjectObject().getID() should do it. Of course, it depends on where you're running it - I've assumed the script has an issue in mind (a post-function, condition or validator for example)
-
What App are you using to provide the "calculated text field"?
-
<sigh> I was answering your question about how it works, not talking about user experiences. For what it's worth though, systems that have status as a simple editable field tend to have really poor data quality about the status because users don't have to think about it and just set what they want and forget it.
-
Yep, a lot of us don't do it "properly". When we don't, we run into problems with tools that are built to support doing it properly, and often don't have functions for our way of doing it. Jira is one of those tools. It's a lot more flexible than many of its competitors, but it's still built for "real" scrum, which only…
-
Again, velocity is how you perform against a set of goals during a set period of time and is used to compare with other non-overlapping periods of the same length. Kanban does not have a start or end date/time, or a commitment. So there's no way to usefully define a velocity and hence burndown. A burndown chart needs a…
-
Try the "advanced search", specifically in this case: Project = A or (project = B and assignee = Mary)
-
Mmm, possibly. An option name can be up to 80 characters, but not all of that will display everywhere if the field width doesn't fit it (and that can vary because of browser sizing etc)
-
You can't add a folder, you have to select the files you want to attach to a page and drop them in (a multiple selection is fine)
-
Ok, that's good, it means the basics are all working correctly. Service Desk lives under the Jira domain, so the paths to it have to be relative. You can't relocate the portals to other places (yet), so you need to allow access on the portal url and above it (i.e. the rest of Jira) You could however close off access to…
-
In a working postgres service, the files would be created and managed by the database service. there's no reason for them to be deleted. I don't know how they might get deleted, I wouldn't expect the database to do it unless tables or possibly an entire database were dropped. I have seen files go missing when a disk filled…
-
The log has given you the name of the first file that is missing from the database server. But I'm not a postgres expert, I don't know where it keeps files or what is in them
-
It's one of the reasons the behaviour module in Scriptrunner was written - because Jira does not have functions to show/hide fields. A lot of people use Behaviours for this.
-
Plugin .jar files do not change because they are licenced. They are added to <jira home>/plugins and stay there, whether unlicenced, evaluated or fully licenced. It is safer and better to use the "add add-on" functions in the UI than to mess around with files and directories though.
-
There's not a lot you can do other than find the missing files on the database. It might be incorrect permissions, not actually "file not there". If you can't find the fiels, then you'll need to start thinking about restoring from backups.
-
Yes, you can do this in one upload if you create an archive of some sort and attach that. Or you could flatten your "folders" into a single list of files and then attach all of them in one go.
-
Yes, that's correct. Status is not a field, it's an indication of where the issue is in the process. You can't "edit" it, because it's not a field, you need to move the issue through transitions to update it.
-
That looks like there is something wrong with your database - the file it's referring to is a file the database keeps data in. You'll need to talk to your DBAs about why it's missing.
-
This suggests Jira is using a protocol for SSL that the mail server does not understand/support. What protocols does the mail server support for SSL?