Comments
-
It's up to your process. I'd usually say a new feature often doesn't need an affects version, because it's something new, rather than something broken in a specific version. But in some cases, it might be useful to refer to a specific version.
-
You need to establish where Input is not valid, only support is coming from. Do you have a value of "input" anywhere in your CSV?
-
That's a warning rather than an error. It should really be fixed, but it's not the cause of your problem. What other errors are you getting at the time the UI failed to create the project?
-
It does. Because RedHat 7.3 can support the version of Java you need.
-
Nothing technical will stop them. Most people won't do it, but if you do find yourself getting nothing but P1 calls, then you should try education first. "If you raise everything as P1, we're simply going to prioritise them in the order you (and other clients) raise them, and/or edit them down". Or you could reach for a…
-
Generally, I see several solutions to this, but they tend to boil down into three general approaches. 1. Let the customers set the priority, but train your agents to correct it. 2. Work out SLAs differently, not based on priority 3. Calculate it - offer the customer different fields and work out the priority from them.…
-
The best I can do is suggest you put the validator on more transitions, as that will force people to put the epic link in before they can move it on through the workflow.
-
No. Jira doesn't do "field level security" off-the-shelf. There are some ways to protect edits, but the users will see all data. The general solution to this is a low security "use Behaviours or hacky javascript to stop it", the secure "move the edits into the workflow so you can place conditions on them", or to try out…
-
The email handlers cannot begin to guess where an email may be bound, and they pick up mail asynchronously - for any given email, you can't say which handler will get to it first. The handlers all have the "project" setting, so the first handler to catch any email will create it in their project. The way to handle multiple…
-
So you can create a sub-task of type "sub task" in the UI, and that is what you told the post-function to create as well?
-
You need to read the Jira logs. Look at the Jira system's config in the system information pages, it will tell you where the log is.
-
Hmm. That's definitely a bug. You must be slightly ahead of my Cloud instance, where "no browse = no sign of project anywhere" I'd definitely raise this with https://support.atlassian.com/contact
-
If you set a class to a DEBUG level, you'll get a tonne of information dumped out to the log. At a debug level, just about everything is logged, but it will fill your disk and slow the service down, so use it sparingly.
-
It is the project you define in the handler. If you include an existing issue key in the subject, then it will comment on that issue. Otherwise, it will create a new issue in that project. Are you seeing it create in other projects?
-
There's a couple of points here. Plain core Jira considers an issue resolved when the "resolution" field is not empty. It does not care what is in there, just that there is something. It does not look at sprints, boards or even status. Just the content (or lack of content) in the resolution field. A board however uses a…
-
You can get the log location from the system information page in admin. It's usually atlassian-jira.log under <jira home>/logs
-
I'm using Cloud too, and I don't have this problem. Could you show us what your users are seeing for a "closed" project?
-
Where they are used in user picker fields (assignee, reporter and any custom fields), you can use bulk-edit to change it. It's a bit more difficult for multi-user pickers if you have any of those. You won't be able to change the comments or issue history.
-
Under <Jira home>/logs. You can get the full location from Jira's System Information page in the admin section.
-
The long answer is that you need to remove the default "everyone who can log in automatically gets access to projects" by removing the "can log in" group from the roles of every project, replacing them with other groups that give the right users access. But a quick fix here is to create a new group, put your user in it and…
-
You'll need to check what the scheme is doing - it should limit "browse project". Check the rule in there for who has permission to browse the project and then check the settings for the project.
-
An internal server error means something went wrong in Jira, not your code. You'll need to read the Jira logs to discover what it was.
-
It depends on what you arranged with your vendor. Did you agree to get the licences through them? A lot of Solution partners and and 3rd parties will buy licences for you. There's no difference as far as the software or Atlassian are concerned - you have a valid licence.
-
On your test issue, can you create a sub-task? Is that the same type as you have configured for the post-function?
-
It bites me every time I edit workflows!
-
You'll need to read the logs to find out the detail of what is going wrong. Have a look in <jira home>/logs - start with atlassian-jira.log, and read it for the time at which you got the error.
-
Have you published the drafted workflow?
-
Absolutely. You can do almost anything with add-ons for Jira. Lots of people have already, although you'll find most of the stuff on the marketplace is for issues, rather than users (it sounds like you want to export user data?)
-
>For now jira accept only users that connect from company machine(company ip adress). Ok, that's a matter for your network people. Jira is firewalled (or possibly routed) away from the internet, so only systems inside your network can get to it. Either your network team needs to change the firewalls and routing to allow…
-
Fix version is a system field, most of which don't hide themselves. It's inconsistent and annoying!