Comments
- 1-15 of 15
Workaround worked like a charm. Thanks Jen!
Thanks for the tip Dheeraj. I guess I never thought of using raw html.
One concern I have with this approach is potential name collisions with whatever Mingle might be using.
I did run into what seems to be a Firefox problem with intrapage links... even if I navigate to www.company.com/mypage#middle, Firefox starts off at the top. If I enter the url directly, it seems to work fine. And it works fine in IE.
I used the following format:
On "mywikipage" I have the following:
h2. <a id="middle">The middle part</a>
On my page with the link, I have the following:
"my link":http://mymingle:8080/project/myproject/wiki/mywikipage#middle
When I click on the link, I get to the top of the page. If I position the cursor on the url and hit enter, firefox then takes me to the right place.
I would also like to see this feature implemented.
I just discovered the history tab available when viewing a specific card. It’s next to the Comments tab on the right hand side of the view. I didn’t know this existed. Though I still think it would be useful to have a card-number property available on the history filter, having the ability to view history in the card view gives me the capability I need. If you add this to your story list, please mark it as very low priority. Thanks.
Thanks Dheeraj. I hadn’t thought of using a transition… that’s a great idea. Alas, I had already manually deleted them through the tree_belongings table before I saw your suggestions.
Makes sense. Thanks for the explanation.
Update on second problem: I was able to hack around the “cannot change card type” issue by temporarily changing the “Add To Current Release” transition to eliminate the setting of the release to (current release). I changed it to (no change), did the import, then changed it back.
Thanks for the response Suzie. Good to know I’m not going nuts.
Second problem now. I tried importing my data without incorporating the story tree. That is, I specified ‘no’ in the ‘Planning Tree’ column and did not specify the tree related properties. I figured I could manually specify the tree relationship once the data gets imported. Now I get an error for each row (where [i] = 1..n) that says “Row [i]: Cannot change card type because card is being used in transition: Add to Current Release”.
I’m not sure why importing would be prevented simply by virtue of the fact that a card is a potential participant in a transition. Is this expected behavior? If so, can you help me understand why?
Thanks.
My resolution is 1440×900.
Hi Suzie.
I would definitely expect the value and comment to be applied to all cards in the transition. I would NOT want to have to enter the same information for each card in the bulk update. If I needed different values for different transitions, I would perform multiple bulk updates.
It may be useful to put a message in the input box that warns users that the input data will be applied to all cards in the bulk action.
Thanks.
You’re right on the mark. I missed that renaming of the relationship. When I went back and renamed the relationship from “story” to “goal”, all was well. Thanks.
+1 on being able to color and sort by tree relationship properties (e.g. iteration card)
OK, I figured out what my problem was and got it to work – my indentation was off. It appears that the parameters for each line must be indented. That is, instead of this:
- label: Total Scope
color: black
type: line
data: SELECT ‘Added to Scope On’, SUMIt must look like this:
- label: Total Scope color: black type: line data: SELECT ‘Added to Scope On’, SUM
So several issues flow here:
1) If the indentation is truly necessary, the examples in the help files should be modified to illustrate the indentation. (I copied from the help text to get myself started, and there is no indentation in the help file examples).
2) It would be helpful to describe the indentation requirements in the help files – particularly for the charts.
3) The Ruby error message (undefined method ‘collect’) should be caught and filtered.
Thanks.
That’s a reasonable work-around. Thanks for the response.
Thanks Suzie. I thought I had tried this before – it is the most logical solution. When I tried it again it worked. Perhaps I had a typo in my name. Perhaps you were sending good vibes my way. In any case, I’m good now. Thanks.