Comments
-
As Norman says, it's well worth thinking about the long term. A good approach is to have "incidents" which essentially go through status like: * New bad thing happen * Support is looking at it * It works now ... However, there's a whole second phase which is often neglected * We don't know why * We do know why, and we need…
-
At it's most basic usage, Jira is an "issue tracker". Most people use it more as a "bug tracker", which is one use for an issue tracker, but it can easily be used to track "incidents" as well. Exactly as you say, each time system X goes "bang", you raise a new incident. When your team puts out the fire, you move it to a…
-
"Ticket" is a word used in the IT industry to represent "something that someone needs to look at". It's a really bad choice of word, because the English word "ticket" is not in the slightest bit representative of that concept, but sadly, we're stuck with it. In this case, your "ticket" has been raised and tracked in…
-
This isn't Atlassian support, this is the community of users. We can't do anything with your OnDemand installation, and we can't really give you much help unless you can tell us exactly what you're trying to do and where the problem is. It sounds like you're asking for some non-standard process here though, so I'm not…
-
It's not clear what you want here. You have referred to a document about the two reasons a "forgot password" option might not be available to a confluence user, but the question doesn't seem to be about that. Please explain what you mean by "missing" in this question
-
Yes, Confluence is an application. I suspect you need to explain what you're actually looking for here?
-
You can do the internal linking, but that's not really going to help much, as you can't report on it. Even if you did some epic linking, JIRA doesn't consider estimates on sub-tasks, only stories, so it's not going to help you with the reporting.
-
It's an integral part of Confluence, and the collaboration stuff is layered on top of it. You'd have to work out a way to package that up out of Confluence and add it into your application. It's also written in languages that you'll struggle to run within ASP.NET. So, I'd probably want to say "no"
-
You need to repeat the change in each email template that you want it to appear on. Make the same changes to the "comment" .vm as you've made in the "create" .vm
-
It gives you the friendly human text if the date is within the last week (and the exact one if you hover over the date) To turn it off, see https://confluence.atlassian.com/display/JIRA/__date+and+time+formats but beat in mind this is a global setting.
-
Could you check * The list of enabled system add-ons to see if there are any partially or totally disabled in there * The log file at start up - any warnings or errors about not being able to load stuff
-
You can't. The workflows only support one create transition, and by definition a transition only has one end point. I was going to start on processes that can transition an issue after creation (which you can't do on Cloud), but actually, you have a better option, which you've already started to think about. You can create…
-
Agile is mostly a view on to Jira data. The stuff you see in Agile is 99% just a different view of the Jira data. Agile relies on some functions that are core Jira well - specifically, you will *always* be using Jira if you do any filtering. Or creating projects. Or using Dashboards or walls, or admin functions, or or…
-
I am terribly sorry that you've suffered the Daily Mail. (For any Americans reading this thread who haven't read it, it's the equivalent of Fox "News" - wildly inaccurate and horribly bigoted )
-
Completely stolen from "The Oatmeal" (Certainly the style, if not the exact words). Although I have worked for some people heading that way. I don't know if you're familiar with UK newspapers, but one of my worst examples of that caricature could be explained by saying "he used to work for the Daily Mail"
-
I should have emphasised that my approach was thinking of one specific client, and it was the "solution" we arrived at there as being the most effective. For them. You should always judge the approach for *your* user base.Daniel's point about Carrot and Stick is a really good way to put it too, just make sure the carrot…
-
There's loads of variations on this, but I would: * Be nice to them. Set up a standard email handler so that their emails are imported as comments when the subject of their email contains an issue ID. This won't encourage them to use JIRA, but it does mean that they won't feel neglected or ignored when responding to JIRA…
-
No, a workflow can only have one entry point - a single starting status. There are some options, the usual one is to use something like the automation add-on or Script Runner to detect some data on the new issue and auto-transition it to another status within the workflow.
-
>the text that auto populates in the Project Brief Field Project Brief is not a system field, so it must be a field you (or another admin) has added it. As it's a custom field, I would guess that they've set a default value for it, so look at Admin -> Custom Fields -> Project Brief -> Configure
-
You don't associate different fields with transitions directly. You put fields on screens. You associate different screens with transitions.
-
Ok. You cannot really do this. A field belongs to an issue. That's it, it's nothing to do with the workflow. You can, however, control where fields appear. If you look at "screen schemes", you will find that there are three entries - you can tell Jira to use a different "screen" (which is a list of fields to use) for View,…
-
I'm afraid the question is a little unclear. What groups do you mean? (I'd guess at groups of users?) More importantly, what do you mean by "associate with status"? I really don't have any guess for what you might mean by that?
-
Agile IS Greenhopper.
-
mmm, I've not tried that, I always use WAR or Standalone. I was thinking specifically of the content of jira.home, I didn't know the launcher would do more outside there.
-
No, it won't work. First, as you've noticed, the server ID will change with each host. On top of that, you need to understand the structure. Although it's a doddle to stick the application somewhere (it doesn't matter as long as it can be read), the data is not readily portably. You'd need to think about how to connect to…
-
Ok, well, it would have been useful to tell us about that earlier. However, that is an error being thrown by a service, not something that is run as part of screen generation, so I would not expect it to be a problem on every page.You still need to try turning off the plugin to see if it changes anything
-
Start with checking that the copy-to-subtask plugin is the right version for your JIRA installation. Secondly, try simple test to see if this is the plugin - remove the copy-to-subtask plugin and see if the performance improves. If it does, then you know it's the plugin. Let us know how you get on with those two, and then…
-
Not at all. I thought you had JIRA running, but throwing errors, so I was assuming you could go to the plugin manager and disable it, but it sounds like you couldn't get that far. So nice catch on removing it from the file system!
-
Answers emails people who have participated The problem you've got here appears to be from a git related plugin - https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/server/overview It sounds like the rest of JIRA is working, so a quick test before we go off chasing the wrong thing down the wrong…
-
Ok, you might need to check your database setup and connections, but we could do with a good chunk more of the log - to see what it was trying to do when it failed to hit the database.