Comments
-
Nope, similar problem. You've already run into the clumsy workaround by blocking it in the workflow. But it is a bit easier. I think the behaviours plugin can do this for you. There's also the possibility of javascript to remove the option on the client side, but generally hacking javascript into Jira is a bit of a pain,…
-
Oh, I like the easy ones. No. There's no way to do this without hacking the core code, and it's complex enough that it's not something I'd even try!
-
Start with a look at the filter - what is the definitiion, are there things in there that might vary? Next, read the log file for errors while you're doing this. Whatever is causing this, it's likely to be index related, so we're looking for errors in that area.
-
There is absolutely no way to do this in Jira without doing some significant hacking in the core code. The whole thing is structured on "issue type uses workflow". (By the way, I could ramble a lot about the idea, but Nick Massette and Joe Pitt have already said most of what I wanted to say) It is an interesting idea…
-
Simple project boards are not as flexible or configurable as Kanban boards. You can't do the more advanced config on them.
-
The history (And transition, if you have the Jira toolkit installed) is definitely the best way to check your data. It's not really logged as such, but the history really should record everything. This is why I'm flummoxed. You have done everything right, you've checked all the places you can, you've followed the setup…
-
The current state doesn't matter The @TransitionId: 741 should mean "when I need to draw this field, go look at the issue history and pull out the last change history item that says the issue went through a transition with an ID of 741". (An event will be fired automatically, but it's nothing to do with this field) As long…
-
Sorry, cross posted - started typing, got distracted, came back, didn't see your update. That warning message is very helpful, ish. It tells us that the field is doesn't have any data. Can you confirm that your issue definitely has been through the verified transition? Check the history tab on the issue.
-
S'ok, we can sort of work without that, as there's a few... Let's pick on an issue that you know goes through the transition you've selected (are you sure 711 is the right number, by the way?) Go to the project header for it and look for the issue-type-screen-scheme Click on that, then go into the screen-scheme for the…
-
Ok. So, what screen have you added it to? Have you checked that this screen is definitely the one in use for issue VIEW in this project? Now we know which type of field it is, and the config is quite complex and text-based, could you post the exact config you have placed for it
-
What do you mean by "transition date/time" field? Standard custom fields include a date/time, but they are for entering data into (and won't be displayed until you have put data in) So I'm guessing you have a plugin providing this somehow? Unless I've missed something in the core of course. If it is a plugin that you've…
-
Add them to the "admin" group. If you mean system admin, then you can not do this. System admin rights are limited to Atlassian support.
-
The project must be enabled for Agile (a lot of places simply say "all projects", but it is possible to restrict it to a list). Have a look in the system Agile admin area.
-
For additional reassurance - I've done this several times, and had the same experience as Rodrigo - it sails through. Minimal step changes in my case - *just* the database upgrade, moving hardware and/or OS done as a different step, but upgrading MySQL 5.1 to 5.5 is very stable.And I'd echo "test it" and "5.6 is a…
-
Try /home/ec2-user, although as you are probably logging in as ec2-user, you should usually find that you are already there when you first log in. Use pwd to show the current location and cd to change.
-
No. System admin rights give you system administration rights. That's it. (Admin can see/do everything automatically is a dreadful access model for all sorts of reasons and one that Atlassian have rightly stayed away from) If you want access to a project, you need to grant yourself project rights.
-
JIRA Service Desk needs to know basic details about a user - there has to be a user "object" for it to work with. So you have to have a sign-up of some sort. If you were to allow anonymous access, then you'd still need some way to capture contact and response details. So you might as well do it with an account.
-
Sorry, I drifted off-point and was not too clear. You can not just clone or migrate within Cloud, you have to extract and re-load it all in a target system. Start at https://confluence.atlassian.com/display/CLOUDKB/Changing+the+Cloud+Instance+URL+Address+or+Migrating+to+a+New+Cloud+Instance
-
Yes - all you need to do is take a backup of their stuff, then you can restore that on your own (Either buy new Cloud systems to host it, or run your own servers) You could even be more cheeky - if they don't need the sites, maybe you could take ownership of them?
-
Go into your www.my.atlassian.com account (the one you created the OnDemand system with) and look for the licences, you'll find the option to increase to 25 on your existing system. It is written like it's "new", but your existing licences will be taken into account.
-
Hmm, now that's an interesting one. You've got stuff set up correctly as far as I can tell from what you've said (which is pretty detailed). So, just to confirm, you go into the navigator and pick out an issue which definitely has a resolution set when you go into the issue view, but the issue-id is not struck out?
-
If it works in Agile and not in the issue navigator, then you've probably got customised code. However, you should first check the resolutions are set or not, and you don't have broken resolutions like "unresolved" or "not done"
-
Have you any customisations in the code? (Specifically, the last time this came up, someone had changed the css to deliberately remove the strikethrough - obviously quite dumb as they'd not educated the users about the downgrade). Also, you are definitely looking at the *system* resolution field? Not a custom field with…
-
Yes, that's why you don't put it on the screen.
-
Actually, workflow properties are overkill and over-complex for this. If you look at a transtion, you'll see you can add "conditions". These allow or deny people to perform transitions based on all sorts of rules. The really easy one is "only allow current assignee". "Only allow if user is part of a group" is another. You…
-
One nice trick is to keep the default dashboard really basic, but include a text gadget that says "look, here's some other nice dashboards you might prefer to use, or look at the options in the cog to create your own". Giving people a range of shared dashboards to sample really encourages them to find one that works for…
-
Hmm, that's odd, it looks like it's struggling to display the descriptors. I just checked my 4.4 Jira and the plugins you're showing definitely have descriptions, so it's not missing data. What happens if you leave it to process (as it seems to be churning)? Are there any errors in your log files?
-
I'm sorry, I don't understand the question - what do you mean by "push on"? Are you trying to upload something somewhere? Or expanding the plugin details in your Confluence installation? Or have you written a plugin and it's not showing any help or description?
-
I'm not aware of any, sorry.
-
JIRA does not export things in MS Project format. As far as I know, MS Project does not have any code for reading JIRA data. So yes, it is possible to do it without the connector add-on from the marketplace, but you're going to have to write the code to do it in one of the two applications. (Or find an alternative to the…