Comments
-
No. A subtask belongs to its parent, and the parent belongs in a project. So the subtask cannot be in a separate project. Part of this is due to the configuration, it would be an absolute nightmare to have subtasks in other projects because you'd run into permissions issues, different fields, workflows and so-on. The…
-
How does it handle the single-select field then? That's the same list of options.
-
Depends - could you tell us how you're coding? Is it a plugin in one Jira or the other, or an external something? I doubt it though, because most of the APIs expose the field options via id, not name (because the name can change)
-
Look at the Epic and click "edit". Or even just click on the priority for inline edit.
-
Yes. JIRA doesn't care where the database is (as long as the network link is fast and stable enough) 2014 is not yet fully supported, but I'd expect it to be the same as 2012 at this point - see https://confluence.atlassian.com/display/JIRA/Connecting+JIRA+to+SQL+Server+2012
-
It's not an Atlassian add-on really, it's by Spartez. I'd actually re-ask this question, but with a tag of addon-com.spartez.jira.plugins.bork.tfs4jira as I think Spartez monitor that. Also, it might be worth raising the exact request on their issue tracker.
-
Sounds like there could be a corrupted user account, one that begins with an L
-
You'll need to dabble in a spot of coding to do this - it's not surpressable with a flag or setting.
-
You'll need to get in touch with your administrators to find out why you can't log in.
-
The best way to do this is to log into JIRA and use it - oddly, it has a submission form that creates issues. If you want to code something else to gather issues, then * Look at issue collectors * Check out Atlassian Capture * Write something that posts issues into JIRA via the REST interface
-
Oh, and what Joe just said - you should limit issue delete rights to... well, no-one really. Even your admins. They should re-enable it for themselves briefly if there's a real necessity.
-
No. It's gone. There's nothing left of the issue in the database. The only way to track deletes is to plough through access logs. Which might not have enough detail, and aren't accessible to OnDemand users as far as I can tell. You could raise a request with OnDemand support, but I don't know if they'll be able to help.
-
https://confluence.atlassian.com/jira/creating-issues-and-comments-from-email-185729464.html#CreatingIssuesandCommentsfromEmail-Addacommentfromthenonquotedemailbody mentions three handlers that only comment, without create.
-
Right, if you're going to want more than 1,000 lines, you will need to find/write something that can page over the lists and get them in blocks. I'd use Bob Swift's CLI add-on to do it - you can use that to pull the data over a simple connection and then write a few lines of script on the client machine to put them…
-
Moving to Windows just because you think you need it to do extracts is a lot of work for no reward - there are LOADS of ways of doing extracts.Please could you explain what the extracts are?
-
>If we can use windows version of JIRA we can use command prompt to extract the data. That doesn't make a lot of sense. You can use anything to extract data from JIRA - direct database reads, although not recommended, are OS independent. The REST interface is OS independent. The XML and RSS outputs are OS independent, Bob…
-
There is no single project export, so yes, you generally need to work with the full export. Combine the built-in project import with an add-on from Botron or Awnba, and the process, although still lengthy, is relatively straightforward.
-
Um, "I've already asked two questions provoked by this error" - that really does make it sound like you're asking the same thing over and over. I had to look at your profile history to establish that they were different subjects. I very much doubt the ratio you've got there as well. I suspect it's more likely to be 100…
-
First, give Atlassian a chance. Asking three questions at the same time on the same subject isn't giving anyone much of a chance to respond. Secondly, we are a community of end-users, not Atlassian. Atlassian are active here, but there's no guarantees that they will see your posting and they are under no obligation to…
-
Anyway, have you managed to get anywhere with the actual question? Now that I've (hopefully) explained that the issues are separated, does it make sense that you need to think about how to link them?
-
>see you were able to answer my question making some reasonable assumptions based on your experience with other carriers No. I was able to guess what you meant after you provided more information. >Your condescending tone Fair point, I do get condescending when people are rude to me when it's pointed out to them that they…
-
Right, now you've partially explained a load of stuff you had not bothered to explain before, we can try to help. >the research workflow has two transitions Ok. From which status? To where? (Not that we actually need that particularly, having worked through the rest of your update, it's just pointing out that you did not…
-
I'm afraid you have not given us any context here. Research issues and defects are not standard JIRA issues, so you've added them, and you'll need to explain what they are for and how you've configured them. And then when it "automatically closes", what you mean by "no context" and what you mean by "no link" (especially as…
-
No, and you don't want to either - the point is, they don't want you to. You can advise them to do it, which leaves the choice with them, but inflicting your opinion on them is absolutely the wrong thing to do. For new users, I'd be tempted to have "default favourites" if the functionality existed, but not push to existing…
-
You can't. Favourite filters are a personal thing, not for an admin to set. There is a big weakness in Jira's filter management. As designed, it's great, until a user leaves, at which point, the lack of "admin can change other people's filters" becomes a bit of a nightmare. There's a general catch-all improvement for admin…
-
You have a validator in the workflow that says "you must put in a value for Resolution Details" Edit the workflow, find it on the "submit for review" transition, and remove it.
-
Those are two separate fields, not one. The best you can do is make the appearance of one field dependent on the other. Try the "behaviours" functions in the Script runner add-on, that's the easiest way to do it.
-
See https://confluence.atlassian.com/cloud/atlassian-cloud-storage-policy-744721619.html
-
Duplicated by https://answers.atlassian.com/questions/43344184
-
It might be that the fields were only "deleted" from screens or a field config was changed to hide them - if that's the case, the data is still there, just need to undo those changes.