Comments
-
Your users will struggle with fielditis well before the service will.
-
I'd always reach out for an Atlassian expert partner in cases like this. The directory is at https://www.atlassian.com/experts (Yes, I work for one of them, so I could do the "free advert" thing, but you should base your choice on your needs rather than just activity here)
-
The default reporter should be used when JIRA can't identify the sender as a JIRA user.
-
I'd configure the mail handler to create the issues as a reporter user.
-
I said "most" ;-) That bit isn't quite there yet from what I've seen, although the in-line edit for issues introduced in 5 implies that it could be done, and probably will be.
-
Um, most of that is in Jira 5.2
-
Right, so it's nothing to do with page history or versions. You are looking for something that can present Confluence pages or spaces as a set of docs directly related to an event such as a software release. I think you need to look at something like "Scroll versions".
-
I don't quite understand the question. When you look at a confluence page, you are always looking at the current version (i.e. "newer"). The url for a page does not change when you edit it and create a newer version. To look at older versions of a page, you have to be digging through the page history. Which has a link to…
-
I am sorry I cannot answer you in French, to my shame I can't speak it well enough to avoid embarrassment. To trial Tempo, log into your test system as an administrator, and find "manage addons". There's a section for "find new addons". Search for Tempo in there and click the installation option. It will take you through…
-
That means that the server is not responding to you. It's either not configured to listen to you on the connection you've configured in JIRA, or your network is not delivering a connection. Check your connection settings and test them with ping, tracrt and telnet to see if the server does respond.
-
Yes, I voted on that one ages ago (I couldn't remember where it was when I answered before, otherwise I'd have dredged it up - I've voted on so many)
-
I'm afraid filters belong to a single user.
-
If by "site name", you mean the url for Cloud, then the answer is no, but yes. You can't change the url directly (yet), but you can do it by buying a new Cloud site with the new name, export the old site, import it into the new one and shut down the old. If it's not the url you mean, then could you explain what you mean by…
-
So you can check the workflow and permissions yourself. You will almost certainly find that you don't have the right permissions to progress through the workflow. When you look at a transition like "close", you will find is has a "condition" on it that says something sensible like "only users with the CLOSE permission can…
-
You don't have the permissions to use those workflow actions then. Get your admins to check the workflow and permission schemes in the project. Check if you can do it for other issues in the project as well - that's useful to know.
-
The point of Norman's question here was to check that "Testing" is on the list, so posting something that doesn't show it really misses the whole point. As a generalisation, when you have a complex SQL query that is returning something you don't expect (in this case, it's definitely not giving you anything useful), then…
-
Um, "Testing" doesn't exist...
-
That'll work on Jira 4.x as well as all the way up to 5.1 I wanted to comment for clarity - both the os_workflow (Norman) and the change-history (me) methods of finding a previous status are valid - this is one of the few places where Jira effectively duplicates information (albeit in very different data structures). You…
-
I can't give you the exact SQL, my SQL skills are pretty basic. I can tell you where to look though. The tables you need are changeitem, changegroup and jiraissue. If the status of an issue has never changed, then read Jiraissue, because it has the current status (you'll need to read the status table for the name of the…
-
<sigh> What do your logs say?
-
Ok, good, then yes, you should be able to upgrade Jira quite a bit, while leaving Confluence as it is. My worry was that you might be using Jira's user database for Confluence users - if you take Jira higher than 4.2, you have to upgrade Confluence to 3.5 first (or do a really dodgy hack in the Confluence code...) Be sure…
-
Possibly. What exactly is your version of Confluence, and how are you doing user access? (Crowd/LDAP/Jira database/other)
-
Do you mean you want an email to arrive in JIRA and be attached as a whole message instead of being parsed into the description and summary fields?
-
It's the code in the post functions - some are not appropriate for "create" and tell Jira they aren't valid. So, you can't "get all post functions", some of them deliberately yell "I'm not appropriate here" and so Jira won't let you add them.
-
If you want to drop an issue into a status on the board, you MUST include it on the board. By definition. If you put many status into one column (which is perfectly valid), JIRA splits the column into different sections, one per status, when you pick up a card that can go into the column for dragging.
-
Set up a second instance of JIRA, export the main JIRA data to XML and import the projects you want to "archive" in the new instance. In the second JIRA, have a read-only permission scheme. Once the data is archived in the second JIRA, delete the projects from the first one. Do not try to do this at a database level - you…
-
Yes, you will need a workflow with each user as a status. Which means editing your workflow every time a user arrives/leaves. However, you say "boards", so I assume you've got the Agile addon? If that's the case, then you can cheat a bit - convert the project to "simplified workflow" - when a new person arrives, add a…
-
No, it's simply not there. You'd need to hack in a implementation yourself, either in your plugin, or into the core of Jira itself. If this is a plugin for your organisation's use, I'd recommend spending the time on upgrading Jira instead of hacking. If it's a plugin to be shared with the world, then I'd adjust the target…
-
And potentially destroy your installation. SQL on a JIRA database is to be avoided at all times. Always use the API. If you must use SQL, plan to shut it all down and take a backup before risking it, and then factor in the time for a full reindex afterwards.
-
Yes, you can solve almost anything with Script Runner (in JIRA, Bitbucket or Confluence at least), but I thought that this was more of a one-off correction than something you'd do a lot. I'm not sure there's a good use-case for doing this a lot, it feels a bit like a broken process. But, I suspect you can still do it. The…