Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added ability to hide completed stories from the task board #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

zenocide17
Copy link

I've added the ability to hide completed User Stories. This is a customization we've built for our internal use on Rally SaaS, but I've seen other desire this on the Rally ideas site. Initiating this Pull Request in the hopes that it can be bundled into the standard task board.

@stephanietanner
Copy link

Hey zenocide17,

I'm a product owner at Rally. I examined the code for the task board and we cannot replace the current version with yours. Take a look at this code snippet.

        switch(value.FormattedID.substring(0,2))

        {

            case "US":

                storyType = "userstory";

                break;

            case "DE":

                storyType = "defect";

                break;

        }

Notice the hard coded US and DE. As soon as you change those artifact shorthands the clickable links break. A lot of our customers use 'S' to delineate a user story. Thanks for your pull request!

@zenocide17
Copy link
Author

Thanks for the feedback! I checked the code attached to this issue and commit, and I'm not seeing the code that you have mentioned. Do your concerns apply to #2 ? In either case...

I didn't realize that these were even customizable fields until now! Is there way to programmatically retrieve the User Story and Defect prefix values? If not, is there a way for a custom HTML app to have settings? If so I could tweak the code to have these be configurable values, however I don't know of a way of managing settings in custom HTML apps....

@stephanietanner
Copy link

Yes, they apply to #2. I was looking at the code that you posted on the rally idea. You can get the prefix by querying the type definition endpoint for user stories, tasks and defects. You will need to know the object ID for those type definitions. The query looks something like this: https://rally1.rallydev.com/slm/webservice/1.40/typedefinition/ObjectID.js

Then, you can look for the IDPrefix key in the response and that should get you the values you need for the case in the code snippet above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants