Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/403#issuecomment-35236060
Build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-post y
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/403#issuecomment-35236033
Build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-post
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/403#issuecomment-35236034
Build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-post yo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/403#issuecomment-35236062
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12740/
---
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/403#issuecomment-35236003
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/475#issuecomment-35236088
Maybe Jenkins was down last time. Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/475#issuecomment-35236285
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/475#issuecomment-35236284
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
GitHub user holdenk opened a pull request:
https://github.com/apache/incubator-spark/pull/606
Spark-615: make mapPartitionsWithIndex callable from java
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/incubator-spark
spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/606#issuecomment-35236562
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/606#issuecomment-35236563
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/606#issuecomment-35236630
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/606#issuecomment-35236631
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12742/
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/475#issuecomment-35237920
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/475#issuecomment-35237921
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12741/
---
If you
Hi,
I am trying a Spark Streaming job with a Text File Stream on HDFS with Spark
0.9.0 from cloudera.
I am saving the RDD (100 seconds is streaming frequency) to HDFS in a different
directory. Every 100 seconds, it is creating a new directory in HDFS with
_Success(stream-Random/_Success). But,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/539#issuecomment-35240586
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/539#issuecomment-35240585
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/539#issuecomment-35242604
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12743/
---
If you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/539#issuecomment-35242603
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user NirmalReddy commented on the pull request:
https://github.com/apache/incubator-spark/pull/403#issuecomment-35244753
@aarondav Previously this branch was not in sync with master, now i rebased
it with master. Please comment on it now. Thanks!! (The problem was scalasytle
no
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/539#issuecomment-35247536
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/539#issuecomment-35247537
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user ScrapCodes commented on the pull request:
https://github.com/apache/incubator-spark/pull/539#issuecomment-35247680
I hope nothing is missed out, @mateiz take a look again ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/539#issuecomment-35249277
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12744/
---
If you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/539#issuecomment-35249276
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
GitHub user NirmalReddy opened a pull request:
https://github.com/apache/incubator-spark/pull/607
Added Java API for AsyncRDDActions with tests
Implemented countAsync() , foreachAsync() and foreachPartitionAsync() in
java API . But couldn't find a way to convert FutureAction[Seq[T]]
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/607#issuecomment-35254787
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To
Hi,
In spark-0.9.0-incubating, Master.scala, line 170
logInfo("Registering worker %s:%d with %d cores, %s RAM".format(
host, workerPort, cores, Utils.megabytesToString(memory)))
might need to be corrected to:
logInfo("Registering worker %s:%d with %d cores, %s RAM".format(
Github user punya commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35301961
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-pos
GitHub user ash211 opened a pull request:
https://github.com/apache/incubator-spark/pull/608
Worker registration logging fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/incubator-spark patch-7
Alternatively you can re
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/608#issuecomment-35304080
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/608#issuecomment-35304081
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Hi dachuan,
At first glance that does look like a bug. I've opened a pull request with
the change here:
https://github.com/apache/incubator-spark/pull/608
Is that the fix you're proposing?
Thanks!
Andrew
On Mon, Feb 17, 2014 at 6:56 AM, dachuan wrote:
> Hi,
>
> In spark-0.9.0-incubating, M
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/606#discussion_r9798640
Did you add this class? I don't see it in this PR.
also, nit: the previous style was more correct, putting this parameter on
the next line (and both indented 4
Github user ash211 commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35305383
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-po
Github user ash211 commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35305400
(not sure if that's going to work)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, pleas
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35305983
Jenkins whitelist is separate from Jenkins admins, the latter of which is
explicitly managed by the people who run the AMPLab Jenkins, alas.
Jenkins, ad
right, exactly. thanks!
On Mon, Feb 17, 2014 at 12:18 PM, Andrew Ash wrote:
> Hi dachuan,
>
> At first glance that does look like a bug. I've opened a pull request with
> the change here:
>
> https://github.com/apache/incubator-spark/pull/608
>
> Is that the fix you're proposing?
>
> Thanks!
>
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/608#issuecomment-35306750
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/608#issuecomment-35306751
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12745/
---
If you
Github user shivaram commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35306727
Jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-p
Github user shivaram commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35306867
I am not sure, but I think the add to whitelist works from the next time a
commit is made.
---
If your project is set up for it, you can reply to this email an
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35306967
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12746/
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35306921
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35306920
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35306966
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/403#issuecomment-35307150
Jenkins, add to whitelist and ok to test. (c'mon Jenkins, I believe in you)
---
If your project is set up for it, you can reply to this email and have your
repl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/403#issuecomment-35307412
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/403#issuecomment-35307413
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/607#issuecomment-35307506
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/608#issuecomment-35307471
Thanks!! Merged in master and branch-0.9. We should've listened to the
"suspicious shadowing" warning in the first place, no good comes of those.
---
If your p
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35307803
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/607#issuecomment-35307800
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/607#issuecomment-35307799
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35307804
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Hi dachuan,
Aaron merged this in, so it should be fixed in the next release!
Thanks for the patch!
Andrew
On Mon, Feb 17, 2014 at 9:39 AM, dachuan wrote:
> right, exactly. thanks!
>
>
> On Mon, Feb 17, 2014 at 12:18 PM, Andrew Ash wrote:
>
> > Hi dachuan,
> >
> > At first glance that does lo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35308071
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12749/
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35308070
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/607#issuecomment-35308068
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12748/
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/607#issuecomment-35308067
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user andrewor14 commented on the pull request:
https://github.com/apache/incubator-spark/pull/536#discussion_r9799844
No it's supposed to link to the section called "Where to Go from Here" at
the bottom, so the hash tags for (#where-to-go-from-here) should work. Maybe
it's beca
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/403#issuecomment-35309770
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/403#issuecomment-35309771
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12747/
---
If you
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-spark/pull/608
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-post your response.
If your project does not have this featur
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35310307
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35310306
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/536#issuecomment-35310374
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/536#issuecomment-35310373
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35311100
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12750/
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35311099
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user mengxr commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#discussion_r9800999
I'm not sure which style to use. @rxin ? I prefer the following:
~~~
map { fold => ( // "((" seems to
be unnecessar
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/536#issuecomment-35312592
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/536#issuecomment-35312594
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12751/
---
If you
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#discussion_r9801137
(1 to folds) is preferred, your style is fine though we use 2 space wrapped
indents instead of 4. Would this be possible, though?
```
(1 to folds).map { fo
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/536#issuecomment-35312964
Thanks! Merged into master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-spark/pull/536
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-post your response.
If your project does not have this featur
GitHub user andy327 opened a pull request:
https://github.com/apache/incubator-spark/pull/609
Add Shortest-path computations to graphx.lib with unit tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/incubator-spark fe
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/609#issuecomment-35315474
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To
Github user rxin commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#discussion_r9802309
```scala
(1 to numFolds).map { fold =>
val sampler = new BernoulliSampler[T]((fold-1)/foldsF,fold/foldsF,
complement = false)
val train = new Partition
Github user punya commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35316168
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-pos
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35316245
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35316247
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user pwendell commented on the pull request:
https://github.com/apache/incubator-spark/pull/603#issuecomment-35316947
@mateiz @nicklan - I think it's fine to ask Tachyon to publish this stuff
in their jars. Having Tachyon code inside of the Spark codebase is not good for
a bunc
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35318595
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/12752/
---
If you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35318592
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Github user mateiz commented on the pull request:
https://github.com/apache/incubator-spark/pull/539#issuecomment-35322176
@ScrapCodes so in this version, do we still need the "of" methods or can we
remove those?
---
If your project is set up for it, you can reply to this email and h
Github user punya commented on the pull request:
https://github.com/apache/incubator-spark/pull/605#issuecomment-35322379
@aarondav can I get a review?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-
Github user rxin commented on the pull request:
https://github.com/apache/incubator-spark/pull/572#discussion_r9805702
Basically you want to make sure it is obvious that this returns a tuple
(which can also be done through explicit type declaration but probably simpler
this way)
---
Github user rxin commented on the pull request:
https://github.com/apache/incubator-spark/pull/607#issuecomment-35327669
Thanks for submitting this. One discussion we need to have before merging
this is on the long term support for the async scala APIs. When I added those,
they were m
Github user pwendell commented on the pull request:
https://github.com/apache/incubator-spark/pull/603#issuecomment-35328014
@nicklan @mateiz as an alternative, it might be simplest to just download a
Tachyon package (e.g. don't use maven to deal with this). And have a nice
graceful d
Github user aarondav commented on the pull request:
https://github.com/apache/incubator-spark/pull/599#issuecomment-35331962
Thanks! Merged into master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top
Hey,
I tracked an OOME on our 0.9 standalone master down to the master
making a large byte[] for the output statuses (serializeMapStatuses),
and it getting copied once/executor.
In our case, an RDD had 9,000 partitions, so, 81m shuffle combinations,
with the output status using 1 byte per compres
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-spark/pull/599
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do so, please top-post your response.
If your project does not have this featur
Github user markhamstra commented on the pull request:
https://github.com/apache/incubator-spark/pull/607#issuecomment-35333776
Marking them as experimental for 1.0.0 might not be a bad idea. I don't
get the impression that the async actions are seeing a lot of use yet, so there
may
Hi Folks,
I need to open a JIRA ticket to report the problem I'm about to fix with my
first Spark pull request... Trouble is, once I created a user in the Spark
JIRA and logged in, my Issues menu doesn't have any option for creating an
issue. Can someone please assist?
Thanks,
Bryn
The Create Issue button is in the top header bar in the center, right of
Agil and Capture. Here's what my screen looks like: Is that button not
there for you?
[image: Inline image 1]
On Mon, Feb 17, 2014 at 3:57 PM, Bryn Keller wrote:
> Hi Folks,
>
> I need to open a JIRA ticket to report th
Looks like your image didn't make it, but I don't have any buttons on the
menu bar to the right of Agile and Capture. Here's what I see (if the image
makes it...)
[image: Inline image 1]
On Mon, Feb 17, 2014 at 4:01 PM, Andrew Ash wrote:
> The Create Issue button is in the top header bar in th
I think the mail list block the images?
--
Nan Zhu
On Monday, February 17, 2014 at 7:06 PM, Bryn Keller wrote:
> Looks like your image didn't make it, but I don't have any buttons on the
> menu bar to the right of Agile and Capture. Here's what I see (if the image
> makes it...)
>
>
>
>
Quite possible. The problem I'm really asking about is the fact that I
can't create a JIRA issue. I have no "Create an Issue" button as Andrew was
describing.
Thanks,
Bryn
On Mon, Feb 17, 2014 at 4:52 PM, Nan Zhu wrote:
> I think the mail list block the images?
>
> --
> Nan Zhu
>
>
> On Monday
1 - 100 of 150 matches
Mail list logo
