Comments
-
A slight variation would be to only have two transitions, 1 for "set to 1" and another that goes to a screen with the drop-down, and has a validator on it for "when 1 selected, only pass if user in qa_lead group"
-
The error is definitely caused by the Enhancer add-on - the class throwing the error is from that. I'm afraid it's no good you saying "the plugin is OK", it's either the wrong version or that version has a bug in it. Either way your options are 1. Upgrade to a version that is valid and/or does not have the bug 2. Remove…
-
Ah, that was one of the things it might be. Jot down your list of transitions in the order you want to see them in that menu. (Not status, that list is transitions) Number them in blocks starting at say 10, so 10, 20, 30, 40 etc (Big holes leave room for changes later, because you can insert at 25 for example) Edit the…
-
Ok, thanks. That link takes you to the admin section where you can add fields. Fields belong to issue types in a project (or entire projects, or everything). So, no, you can't add a field to an individual issue. You have to add it to the definition of that type of issue, and then you can put data in it, or leave it empty.
-
No, the lookup functionality only looks through the knowledge base. The main problem is that customers may not be able to see other similar requests, so Jira would have to do a load of work on working out a good list from what the current customer can see, and it would be different to what an agent would see. The results…
-
Add status is only available to boards using "simplified workflow" up until Jira 7.6 (in 7.6+ project admins can make changes to workflow via project admin, if the Jira admins have allowed it). You need to get your administrators to convert the board to use simplified workflows if you want to change the status list via the…
-
What do you mean by "ticket drop down box"? I'm afraid that is too vague a phrase to tell us where you are looking. Do you mean the "manage fields" on the issue create and edit screens that a user sees (and is for customising their view only), or are we looking at the administration area?
-
I am guessing what you mean here is that you have a field that takes on the date/time of "now" when a specific transition happens. If the transition happens again, then it updates the field. The problem here is that a field is a single object. There is nowhere to put the old date in that field, because it's a field that…
-
I work for one of them, so any answer I would give could be seen as biased, or sales like. So, I would start at https://www.atlassian.com/partners/search?page=1 instead of asking me. Personally, I would lean towards ones who can provide a local consultant who can easily visit you if you are interested in training or…
-
No, you have to go to the main issue view and use the transitions there.
-
In general, you don't need it. Jira Software is built for Software Project Management off-the-shelf. Click "create issue", select the right sort of project, add users to it, you have a Software Project ready to use. If you want help with usage and configuration (i.e. modifying it so that it matches your desired process…
-
Create the screens you need in Admin -> Issues -> Screens. Edit the workflow you want to use, looking at each transition where you want to use a screen. You'll find the option to enter a "transition screen", where you can select from the list of screens, including the new ones you have added.
-
Indeed, whilst I'd test 7.7.0 and show it to the users so they can see new things, I would rarely put it into production. Either a lot of rigourous testing would have to happen, or we'd wait to see what the community reports as problematic in it and make a call on 7.7.1 or 7.7.2
-
They worked out what was broken and removed the hack/broken add-on/script that was causing the problem, then re-indexed. If you're having an issue, it would be worth asking properly - a new question, with the error message and a description of when it happens and what it does. A detail-free posting on a 7 year old question…
-
Start at https://developer.atlassian.com/server/jira/platform/jira-rest-api-tutorials-6291593/
-
Which "time stamp update"? Where are you looking? Is there something wrong with the issue history?
-
You are going to need to give us more than a context-free error message
-
Your code is not getting an issue. You will need to fix that.
-
This was asked and answered very recently, see https://community.atlassian.com/t5/Jira-questions/how-to-setup-federation/qaq-p/714314
-
As I said, you need to hide it in Field Configurations that are bot for Epics, and show it in the FCs that are associated with Epics. It sounds like you have not yet separated your field configs in a way to allow this.
-
It varies by system, and "site admin" is different to "jira admin", so we now have to be quite vague about it, or write a long set of "if then else" statements. I agree there should be a quick-link to it in the menu when you've got admin. Not really thought about it before, but you are right. I'd follow…
-
Look for the "hide" option next to it in each field configuration that is not associated with Epics
-
You could remove it from all the screens you don't want it on, but the other (possibly easier) option would be to change the "field configuration" so that they hide it for all but Epics
-
Log in as a Jira Admin. Go to Admin -> System Dashboard (use the . option to search if you can't find it)
-
Ok, that's good and bad news. The good is that you've now pretty much ruled out a problem on the client side. The bad is that it means we need to look at logs and try fussy things that we can't actually do on Cloud. You'll need to raise a support request via https://support.atlassian.com/contact
-
Ah, I see. I'm afraid your browser is, for some reason, sending junk to Trello. Imagine it should be sending xml that is technically correct and has good syntactically correct content, such as <animal>penguin</animal>, but contains nonsense data the browser has sent <animal>light bulb</animal> Could you try a different…
-
There is no "On Demand". It was renamed several years ago to "Cloud".
-
It's inefficient and pointless. If an issue is not there, it's been deleted. Your "downstream tracking" is easy - work on the assumption that if it's not there, it's not there.
-
Only admins see the text view, so the order is unimportant there. Is there a user related reason for re-ordering? If so, where?
-
Jira doesn't have sub-directories, and I'm not sure what you mean by "first testing and the nest" Could you explain what add-on you are using for the testing?